Comments (17)
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.
from pgjdbc-ng.
Thanks for the answer. What are you using now? Vertx?
from pgjdbc-ng.
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?
from pgjdbc-ng.
@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.
from pgjdbc-ng.
@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).
from pgjdbc-ng.
@kdubb I have no issue moving it into org.postgresql. and housing it inside our github repo if that's something that appeals to you.
from pgjdbc-ng.
@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.
from pgjdbc-ng.
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.
from pgjdbc-ng.
@davecramer We have talked about this in the past - at least in person 😃 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.
from pgjdbc-ng.
@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.
from pgjdbc-ng.
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.
from pgjdbc-ng.
@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
from pgjdbc-ng.
PostgreSQL Org + 3-BSD works for me
from pgjdbc-ng.
@raphw Used a bit less pessimistic title. You spurred on a good conversation that we needed to start. 😉
from pgjdbc-ng.
Of course, thanks for taking up the question so quickly and actively!
from pgjdbc-ng.
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.
from pgjdbc-ng.
I've created issue #587 to track the transfer to the PostgreSQL organization.
from pgjdbc-ng.
Related Issues (20)
- Allow underscore _ in the host name of a postgres database HOT 1
- Issue with RDS IAM Role Authentication
- update protocol properties at the time of connection creation
- Does it support MATCH_RECOGNIZE? HOT 4
- SCRAM channel binding check failed HOT 3
- Connection leak when timing out connection attempts
- Transfer to PostgreSQL Organization HOT 20
- Committer approval for transfer of copyright HOT 29
- Prepared statement already exists
- Parameter Parsing fails on concat operator in SQLText#parse
- Version upgrades HOT 2
- Execution of executeUpdate Closes Previously Acquired ResultSet
- NullPointerException on Calling getMoreResults
- Syntax Error with Statement.RETURN_GENERATED_KEYS
- Inconsistency between rs.getType() and stmt.getResultSetType()
- Inconsistent Handling of Invalid setFetchDirection Input between ResultSet and Statement
- ResultSet.beforeFirst() Unexpectedly Succeeds on TYPE_FORWARD_ONLY ResultSet
- Execution of executeUpdate Closes Previously Acquired ResultSet HOT 2
- Unable to create Array of ByteArrays for prepared statement
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pgjdbc-ng.