thx guys for your inputs.
@Jackie, I have to stick to SQLite because of its performance-benefits.
Up to 200MB size, there's quite nothing as fast as (Spatial) SQLites.
Where can I check if SQLite is excluded from Connection Pooling?
Also what I see often, is if I replace a SQLite-File, I cannot see any
e.g. when modifying a layer. So it seems, also schema-definition of the
SQLites are somehow cached.
Also here, restart of Mapguide or renaming the file to a new filename fixes
@Kajar, thx for your hints. Unfortunately SHP is not a format, which can
hold much attributive information, you also need one shapefile for each
featureclass which gets unhandy when dealing with
LARGE databases. My SQLites contain 100-200 feature classes.
Something needs to have changed in the SQLite-Provider, as with the old
MG-Versions re-saving the Feature Source was sufficient.
View this message in context:
Sent from the MapGuide Users mailing list archive at Nabble.com.
mapguide-users mailing list