-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Comments
I would say this is the answer to it. Which is sad because there are also still bugs in this code 🙁 |
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 |
@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 |
@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. |
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 :) |
I've already made a pr to your fork and asked a question in the discussion. |
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. |
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. |
Hello! Sorry for the delay in replying. @ardan-bkennedy and I recently stepped in to help maintain the project. |
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?
The text was updated successfully, but these errors were encountered: