Ok: I've seen the bug: when a connection fails, the dataset list is loaded with the previous existing connection, though the connection box displays the failing connection.
I tried loading several bad connections: it always displays the previous list of dataset, if any was found. Will look at it. I've commited a protection against missing spatialite extension: extent query is not loaded in this case. Thus, I can confirm that partial SQLite support is available even if spatialite extension is not loaded through the current JDBC driver. Have to test for other sqlite binary storages, like WKB or WKT. I guess the current code fails with these columns types. Nicolas On 18 December 2015 at 14:25, <edgar.sol...@web.de> wrote: > Nico, > > On 18.12.2015 14:08, edgar.sol...@web.de wrote: > >> > Also tested opening a spatialite connection first, then an Oracle > one: it also worked. > > hmm, weird.. can you please send me the whole output of the Console when > you start OJ via oj_macos.command ? > > > > ok, skip that. can you try to use spatialite first and then an oracle > connection with invalid login or hostname? > > ..ede > > > ------------------------------------------------------------------------------ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >
------------------------------------------------------------------------------
_______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
