Hi Christian, Thanks for the quick response. I am not sure if this will be of any help or not but I wrote this (very crude) patch to get around the problem:
http://files.opengeo.org/sqlite_jni.c.patch I say "crude" because my C hacking skills leave something to be desired. That and it only handles the HAVE_SQLITE3 path, not the HAVE_SQLITE2 or HAVE_BOTH paths. -Justin Christian Werner wrote: > Justin Deoliveira wrote: > > Justin, > >> I have ran into an issue while using the javasqlite jdbc wrapper. The >> issue can be illustrated with the following code: >> ... > > you're right, I've verified that behaviour with SQLite 3.x databases. > The problem cannot be observed with SQLite 2.x databases. > >> Basically it seems that the result set metdata is not properly >> initialized when a query returns no rows. >> >> I guess my question is is this a bug or is it intended behavior? > > Unintended consequences but present since the initial support > for SQLite 3.x in 2004. Thus let's call it a misfeature. I'm > working on a solution. > > Best regards, > Christian > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
