pgjdbc-ng
pgjdbc-ng copied to clipboard
impossibl
A new JDBC driver for PostgreSQL aimed at supporting the advanced features of JDBC and Postgres
Hi there 😄 We have been noticing a leaked connection under certain circumstances when connecting to a PG database with this driver. Here is the simple program I am connecting...
Version: 0.8.9 I have a table with the column of type `bytea[]` I want to insert the value with a prepared statement into the table. To do that at one...
I was being held up from updating my website by the old version so I compiled it myself. This bumps some of the dependency versions and explains how to publish...
I'd like to add some security / vulnerability scanning into the CI pipeline. As far as I know there's no obvious choice for this. I've used [dependencyCheck](https://github.com/jeremylong/DependencyCheck#900-upgrade-notice), but it's slow,...
- when a $1 or $$foo$$ is within () expression, like a function invocation, parse the $ as plain grammar piece - add a test for this situation which does...
Simple repro ``` PREPARE test_plan AS SELECT hashtext($1) ``` This is legal PSQL, libpq, etc. all allow it. pgjdbc-ng throws this error: ``` Error parsing SQL at position 40 (PREPARE...
Hi, got this error after postgres upgrade to 14 version: Caused by: com.impossibl.postgres.jdbc.PGSQLSimpleException: Connection Error: Timeout starting connection at com.impossibl.postgres.jdbc.ErrorUtils.makeSQLException(ErrorUtils.java:138) at com.impossibl.postgres.jdbc.ConnectionUtil.createConnection(ConnectionUtil.java:326) at com.impossibl.postgres.jdbc.AbstractDataSource.createConnection(AbstractDataSource.java:125) at com.impossibl.postgres.jdbc.PGDataSource.getConnection(PGDataSource.java:71) at com.impossibl.postgres.jdbc.PGDataSource.getConnection(PGDataSource.java:63) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native...
In v0.8.9, every invocation of the `PGDirectConnection#createArrayOf` method queries the database to resolve the `typeName` string to an oid which is then looked up in the `SharedRegistry` instance. When executing...
