pgjdbc-ng
pgjdbc-ng copied to clipboard
impossibl
What's the status and direction of the project?
Hello, thanks for the work on this driver and leveraging asynchronous notify/listen. Unfortunately, the library relies on several outdated dependencies. Is it that nobody maintains this code anymore? Thanks.
Not abandoned but we have migrated all of our usage away from JDBC and therefore my main maintenance motivation has gone away.
I will try to get things updated in the coming week.
Perhaps you would consider re-licensing this project under the Postgres license, which would allow others to more easily continue the (very nice) work you have started?
@xzilla I'm definitely open. It's currently the 3 clause BSD so I'm not sure how that's limiting anything. That being said, I've wanted to move it of this defunct organization for a while now.
@raphw We've moved entirely to Quarkus. So yes we're using the reactive PG driver from the Vert.x platform (which Quarkus is built upon).
@kdubb I have no issue moving it into org.postgresql.
@davecramer That would be a great move. I'll chat with you in the next week or so to get things going. I've got a lot going currently.
FYI, I'm happy to continue maintaining the project as much as I can. It has involved a large amount of effort to start and continue the project from myself and others. I don't want to walk away but as I said I've got lots of time constraints.
Also, the pluggable type engine this driver is built on to support advanced, composite, and custom types might live on; either as an add-on or integrated with the Vert.x driver. Currently the Vert.x driver has little to no support for them.
@davecramer We have talked about this in the past - at least in person :smiley: The question is who will maintain the code in the new repository if @kdubb doesn't have time for it. I'm only working with C and Rust now, so I don't have time to do bigger contributions.
I'm happy to sign over my contributions to a new license if necessary.
@jesperpedersen well that's an excellent question. One possibility is that inside the PostgreSQL org it might get more love. I don't have an answer.
Regardless of maintenance capacity, moving the copyright to a proper organization and possibly relicensing is something that should be done; the obvious first choice would be the PostgreSQL org.
@davecramer The new package name could reflect it in some way. The pluggable type engine is the key part -- ideally it should be ported over
@raphw Used a bit less pessimistic title. You spurred on a good conversation that we needed to start. 😉
Update... If there's a path forward that doesn't include me being the ongoing sole maintainer, I'd be willing to commit to on a new release with some updates, a more appropriate package and a transferred copyright that we can finally move to the PostgreSQL org.
I've created issue #587 to track the transfer to the PostgreSQL organization.