[fdo-dev] GetProviderDatastoreType()

[Traian Stanev]

Jason, I completely agree with you -- if I had it my way I would store everything in MapGuide on the file system, not just data files, but also resource xml files. Looking at the code, you can see that I don't have it my way, hahaha.
 
Anyway, on to the question. It means that you cannot correctly publish a feature source from Map to MapGuide for example. You can move the feature source within the virtual folders in the MapGuide repository without problems. At least, that's how I understand it.
 
Traian

	-----Original Message----- 
	From: Jason Birch [mailto:Jason.Birch at nanaimo.ca] 
	Sent: Thu 10/26/2006 10:17 PM 
	To: dev at fdo.osgeo.org 
	Cc: 
	Subject: RE: [fdo-dev] GetProviderDatastoreType()
	
	
	Managed data stores are annoying anyway :)
	 
	I dislike that the default setup means that I have to upload all of my files (which are available via UNC anyway) instead of just pointing to them.  It goes agains all off my anti-duplication training.  And yes, I've read the whitepaper (and earlier explanations on the MG users list) that tell me how to deal with this manually.
	 
	Hmm. Re-reading your comment Traian.  Does this mean that I can't move the virtual location (folder structure) of the feature source in the repository, or just that I can't move the feature source between servers, or into a package, or?
	 
	
	
	Jason

	 
  _____  

	From: Traian Stanev [mailto:traian.stanev at autodesk.com]
	Sent: Thu 2006-10-26 7:03 PM
	To: dev at fdo.osgeo.org; FDO Developers
	Subject: RE: [fdo-dev] GetProviderDatastoreType()
	
	
	Same question applies to the OGR provider.
	In theory one could wait until the connection is open and figure out what the underlying data source is, but I didn't do that (so far). I just made it return Unknown.
	The downside (and I'm relating something that was explained to me when I asked the same question) is that a MapGuide feature source is not portable when you return Unknown -- meaning that if the connection is to a file, the client logic would know to copy the file also when moving a feature source around. With Unknown, it can't know that so copying a feature source would require manual work by the user. 
	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20061026/d0831f7a/attachment.html