New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spatialite views and SQL selects do not work in DATA #4636
Comments
Problem was in GDAL and corresponding ticket is Issue was found so late that the fix will probably not be included in GDAL 1.10. It means that Mapserver will not be able to utilize Spatialite views or select data from Spatialite tables with SQL if Mapserver is using GDAL 1.10. Old mapfiles will also stop working if they have Spatialite layers with selects. |
Is this a new regression in GDAL 1.10 or has this been around for a while? |
New regression as far as I know but Even must know it better. It can be a side effect of substantial improvements in GDAL Spatialite driver which makes Mapserver very much faster with Spatialite. However, I remember that I used GDAL dev versions with great success last summer so this regression must have happened after that. |
Thanks. I have sent the question to @rouault on the gdal-dev list. Let's see what he says. |
FYI @rouault has issued a GDAL 1.10RC5 that includes the fix. |
This was not a Mapserver issue but GDAL and it has been corrected there. Closing |
Tested with MS4W 3.1.0-beta1.zip which was installed from
http://dl.maptools.org/dl/ms4w/ms4w_3.1.0-beta1.zip
Only DATA "table" works as data source for a Mapserver layer. Views or SQL selects do not work when defined as
DATA "table_view" or
DATA "select geometry from table"
A small test database and corresponding mapfile can be downloaded from
http://latuviitta.org/documents/MS_6.2.1_Spatialite_issue.zip
Spatialite database is of Spatialite 3.0 version and created with Spatialite-gui 1.5.0.
GDAL/OGR has no trouble with the database.
The text was updated successfully, but these errors were encountered: