On 16.12.2015 16:44, Rahkonen Jukka (MML) wrote: > Lähettäjä: edgar.sol...@web.de [mailto:edgar.sol...@web.de] > > >> issue with the sqlite extension libs seems to be that they are loaded by >> sqlite itself. all _we've_ got is the >> sqlite jdbc that seems to have a config switch to turn on autoloading *OR* >> the SELECT load_extension(...); >> *OR* the connection parameter "jdbc:sqlite:/...?spatialite=mod_spatialite" >> (is that processed by >> sqlite or did Larry hack that?). > > I do not believe that SQLite is autoloading anything. Datastore loads > mod_spatialite in > https://sourceforge.net/p/jump-pilot/code/HEAD/tree/core/trunk/src/com/vividsolutions/jump/datastore/spatialite/SpatialiteDSMetadata.java > > and DB Query in > https://sourceforge.net/p/jumpdbqplugin/code/ci/default/tree/src/main/java/org/freevoice/jumpdbqueryextension/spatialite/JumpSpatialiteDbQuery.java#l142 > > No mystery at all but explicit SQL function calls. >
just assumed because of https://sourceforge.net/p/jump-pilot/code/HEAD/tree/core/trunk/src/com/vividsolutions/jump/datastore/spatialite/SpatialiteDataStoreDriver.java#l69 "new SQLiteConfig().enableLoadExtension(true);" but obviously this just autoloads the sqlite native libs. my bad. we should probably add spatialite success load messages for debugging purposes, just to make sure everything went well wrt. loading spatialite. .. ede ------------------------------------------------------------------------------ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
