pgjdbc-ng icon indicating copy to clipboard operation
pgjdbc-ng copied to clipboard

A new JDBC driver for PostgreSQL aimed at supporting the advanced features of JDBC and Postgres

Results 69 pgjdbc-ng issues
Sort by recently updated
recently updated
newest added

Hello. Since Postrges JBDC driver cannot work with stored procedures (only functions) via CallableStatement, I tried pgjdbc-ng one. During the execution of the following code I get the exception: >...

type: enhancement
status: accepted
priority: low

Hi. I've tried to deploy a datasource to wildfly 17.0.1 by putting an xml file in /standalone/deployments. The user guide says this should work: `jdbc:pgsql://my.server.com:5432/my_database` It didn't - it tried...

type: question

The driver should throw these specialized sub-classes when possible. See https://github.com/pgjdbc/pgjdbc/issues/214#issuecomment-63276395 for more information.

type: enhancement

In [https://github.com/impossibl/pgjdbc-ng/releases/tag/v0.8](v0.8) OSGI packaging was removed due to issues #309, #320 and PR #310 We need to determine the most maintainable method of managing OSGI packaging and add it to...

type: enhancement

With Java 8 as the minimum lambda's have been used. @jesperpedersen suggested this might be "bad". If lambda's are to be disallowed, should we be removing anonymous class instances, which...

type: maintenance

I'd like to implement a TransactionalBlobInputStream which takes a BlobInputStream as input and ensures there's an active transaction before calling read() etc., reconnecting and seek()-ing if necessary. Thinking about something...

type: enhancement

Need to start by just putting a translation system into place. Translations can come later.

type: enhancement

Hi, got this NPE after [H2](https://github.com/h2database/h2database) upgrade to 2.2.222 (latest) version: ![pgjdbc-ng-bug](https://github.com/impossibl/pgjdbc-ng/assets/3603492/0b7b78b4-90e8-4b1c-9eb5-9a377b9f4015) This was taken from "H2 Console" subproject, which I use in combination with your driver. So I observed...

According to JDBC specifications, invoking beforeFirst() on a TYPE_FORWARD_ONLY ResultSet should either throw a SQLException or have no effect, as TYPE_FORWARD_ONLY ResultSets do not support cursor movements other than forward....

When an invalid fetch direction value is passed to setFetchDirection, the ResultSet object accepts it without throwing an exception, whereas the Statement object correctly throws a SQLException for the same...