[mapguide-dev] Unmanaged Data APIs RFC

[Jason Birch]

That would be cool.  That way we can have a theme, and a nested hierarchy within that theme if we need the complexity.  Are we restricted to single-word mappings, or will spaces be supported?  ASCII characters only or full internationalisation?
 
What about schema changes?  Will there be a way of updating the repository's knowledge of unmanaged data schemae?  Or are these maybe cached on a session basis like the RDBMS schemae?
 
There would also need to be a method that allows the author UIs to validate resources that reference unmanaged data sources, to make sure that any dependancies (properties, maptips, themes, etc) are still valid, and give a graphical indication when the world slips.
 
Jason

________________________________

From: Robert Bray [mailto:rbray at robertbray.net]
Sent: Thu 2006-11-02 10:46 PM
To: dev at mapguide.osgeo.org
Subject: Re: [mapguide-dev] Unmanaged Data APIs RFC


I too am concerned this will make data management hard for people with lots of data / multiple projects. It might be better to dedicate a section in serverconfig.ini to define path mappings as follows:

[Path Mappings]
SomeSdfFiles = <some path>
SomeShpFiles = <some other path>
BigArseImages = <path to SAN disk>
...

In Studio / Web Studio the user would be presented the list of path mappings. Once they select a path mapping they can browse all files and folders below that path.

My 2 cents...

Bob

--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe at mapguide.osgeo.org For additional commands, e-mail: dev-help at mapguide.osgeo.org 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 4643 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/mapguide-internals/attachments/20061103/cb70538e/attachment.bin