Discussion:
Updating Feature Sources without restarting MG
(too old to reply)
Reservoirdog
2017-05-09 12:03:33 UTC
Permalink
Raw Message
In our company we pretty often update geodata, mainly in form of
SQLite-Files.
So, if e.g. a water-utility is being updated we write a new sqlite-file and
replace the old
one in the repository. If I try to preview the "new" data now, it looks
corrupt.
It only works immediately if the filename is other that the old, or Mapguide
service gets restarted.
In MG 2.6 it was sufficient to save the feature source again, and it showed
the correct "new" data.
Is there any way I can replace sqlite-files while leaving mapguide running
and don't have to rename filenames? I would like to sort of "update" a
feature-source via Maestro or Mapagent...
How do other users handle this "data-update-issue"?

best regards, Chris.



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Updating-Feature-Sources-without-restarting-MG-tp5319874.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Jackie Ng
2017-05-09 17:38:17 UTC
Permalink
Raw Message
Don't use flat-files maybe? They are not designed for concurrent read/write
access from multiple users/applications. This is the kind of scenario that
relational databases are supposed to solve.

But if you must stick with SQLite files in this particular scenario ...
perhaps check whether the OSGeo.SQLite provider has been excluded from
connection pooling. Connection pooling will hold onto and reuse FDO
connections. MapGuide keeping pooled SQLite connections may have kept some
open file handles on the SQLite db, though if that is the case it sounds
like a bug on the SQLite FDO provider end.

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Updating-Feature-Sources-without-restarting-MG-tp5319874p5319951.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Kajar
2017-05-09 20:32:16 UTC
Permalink
Raw Message
I do almost same but using SHP. I wanted to use Sqlite at first, but Autocad
MAP 3d have bug to export to Sqlite using command in command line scripts,
so I was pushed to use SHP. Every night scripts collects information from 80
drawings and creating one SHP from dwg data. So SHP is overwrite the old one
every night.
I'm using connection to SHP not uploading it to repository and for me its
work perfectly.
Maybe you need to use alternative format.

Kajar





--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Updating-Feature-Sources-without-restarting-MG-tp5319874p5319963.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Reservoirdog
2017-05-10 11:07:39 UTC
Permalink
Raw Message
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
Schema-Changes
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
this.

@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: http://osgeo-org.1560.x6.nabble.com/Updating-Feature-Sources-without-restarting-MG-tp5319874p5320030.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Martin Morrison
2017-05-10 12:21:32 UTC
Permalink
Raw Message
SQL server (or Oracle) would be the option I would pick. Updates on the fly and a true RDBMS. Speed should not be an issue with it.

Martin Morrison     
Infrastructure Application Engineer/Systems Analyst
 Engineering Design Systems, Inc.
540.345.1410
***@edsi.com

 
www.edsi.com

-----Original Message-----
From: mapguide-users [mailto:mapguide-users-***@lists.osgeo.org] On Behalf Of Reservoirdog
Sent: Wednesday, May 10, 2017 7:08 AM
To: mapguide-***@lists.osgeo.org
Subject: Re: [mapguide-users] Updating Feature Sources without restarting MG

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 Schema-Changes 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 this.

@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: http://osgeo-org.1560.x6.nabble.com/Updating-Feature-Sources-without-restarting-MG-tp5319874p5320030.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
_______________________________________________
mapguide-users mailing list
mapguide-***@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users
Jackie Ng
2017-05-10 13:22:14 UTC
Permalink
Raw Message
I think it's called DataConnectionPoolExcludedProviders in serverconfig.ini

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Updating-Feature-Sources-without-restarting-MG-tp5319874p5320050.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

Loading...