View Ticket
Not logged in
Ticket Hash: a78db748a293c19e37661e2768f37d14fff1ca5b
Title: InitSpatialMetaData() returns 0, when a gdal/ogr created Metdata-Tables are found
Status: Closed Type: Code_Defect
Severity: Important Priority: Immediate
Subsystem: Resolution: Works_As_Designed
Last Modified: 2018-01-18 04:47:49
Version Found In: 4.3
User Comments:
mj10777 added on 2018-01-17 14:27:20:

InitSpatialMetaData() returns 0, when a Database, contains a 'geometry_columns' and a 'spatial_ref_sys' table created by gdal/ogr.

    it may assume that it is a spatialite version, but is not the case since 'geometry_columns' is different and cannot be used

spatialite_gui, at least, should inform the user that mixing fdo/ogr with spatialite is not possible.
I assume that the user saw the message-box, showing that FdoOgr was active, but did not understand what that entails.


mj10777 added on 2018-01-17 14:28:33:

The reference to the issue:
https://groups.google.com/forum/#!topic/spatialite-users/5rle-yDvAX4


mj10777 added on 2018-01-18 04:47:49:
spatialite_gui informed the user that a valid FDO/OGR DB-file 
is going to be connected, which was ignored.