Skip to content

Is project dead? #878

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
henryx opened this issue Jul 26, 2023 · 9 comments
Closed

Is project dead? #878

henryx opened this issue Jul 26, 2023 · 9 comments

Comments

@henryx
Copy link

henryx commented Jul 26, 2023

Last commit was on April 2022. After this date, nothing changed in the evolution of the project. So, as of today, project is to be considered still alive?

@uvulpos
Copy link

uvulpos commented Jul 29, 2023

https://www.reddit.com/r/golang/comments/l43wn7/comment/gkm42xz/?utm_source=share&utm_medium=web2x&context=3

In my opinion, it's feature complete. There's one major feature I would like to add but can't come up with a good design for. The amount of outstanding issues and PRs is due to my inability to really engage with these with the care I would like, rather than an indicator of problems in the behaviour of the library.

I would say this is the answer to it. Which is sad because there are also still bugs in this code 🙁

@BenKnigge
Copy link

I've forked it for my own needs but have started merging some of the existing pr's into my fork. If either of your would be interested in either creating a fork or helping me with mine let me know. https://github.com/BenKnigge/sqly

@uvulpos
Copy link

uvulpos commented Aug 5, 2023

@BenKnigge I would appreciate it to maintain the project as https://github.com/go-sqlx/sqlx. However, there is an interesting issue in the go src repo speaking about implementing a native solution. This would make sqlx then obsolete. golang/go#61637

@BenKnigge
Copy link

@uvulpos it looks like you have already started to do what I'm just starting to do. A native solution would be nice but sqlx also has named parameters as some other features not mentioned.

@uvulpos
Copy link

uvulpos commented Aug 5, 2023

Yes, I did not use every feature of this library, so it needs to be added now. But we could merge our work together if you'd like to. I invited you as a maintainer to the project if you are interested :)

@BenKnigge
Copy link

I've already made a pr to your fork and asked a question in the discussion.

@PaluMacil
Copy link

No need for a fork. People that used sqlx should mostly use scany now. It's mature, active, and if you use Postgres you can even use the native interface and types, though it supports database/sql for everyone else as well.

@nielskrijger
Copy link

nielskrijger commented Aug 16, 2023

Scany appears to be quite low-maintenance too; it's months between commits.

Granted it's a much simpler lib; but to call it active is a bit of a stretch.

@dlsniper
Copy link
Collaborator

dlsniper commented Feb 1, 2024

Hello! Sorry for the delay in replying. @ardan-bkennedy and I recently stepped in to help maintain the project.
We are in the process of triaging all the opened PRs and then issues, and we plan to address outstanding issues and upgrade the library to support generics and new Go versions, among other things.

@dlsniper dlsniper closed this as completed Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants