On Tue, Mar 12, 2013 at 1:39 PM, Thomas Kellerer <spam_eater@gmx.net> wrote:
Kevin Wooten wrote on 12.03.2013 02:19:
So… I did a crazy thing… I created an entirely new JDBC driver.
(For those who care there's an actual question at the bottom… this isn't just bragging)
I'd love it if some folks in the know could take a look at my code and see if it stirs up any ideas on integration or just makes you want to jump off a bridge.
It does sound very nice, thanks very much for the effort!
I didn't look at the code, but one thing I noticed when trying the driver is that it requires a bunch of other libraries which is highly unusual in the JDBC "world". Usually the JDBC driver jar is self contained.
When I tried it with my SQL tool (SQL Workbench/J) I got the following exception when connecting:
java.lang.NullPointerException at com.impossibl.postgres.protocol.v30.ProtocolImpl.sendStartup(ProtocolImpl.java:168) at com.impossibl.postgres.protocol.v30.StartupCommandImpl.execute(StartupCommandImpl.java:107) at com.impossibl.postgres.protocol.v30.ProtocolImpl.execute(ProtocolImpl.java:139) at com.impossibl.postgres.system.BasicContext.start(BasicContext.java:151) at com.impossibl.postgres.system.BasicContext.init(BasicContext.java:110) at com.impossibl.postgres.jdbc.PSQLDriver.connect(PSQLDriver.java:56) at com.impossibl.postgres.jdbc.PSQLDriver.connect(PSQLDriver.java:22)
