[fdo-dev] GetProviderDatastoreType()

Traian Stanev traian.stanev at autodesk.com
Thu Oct 26 22:03:53 EDT 2006

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. 

	-----Original Message----- 
	From: Frank Warmerdam (External) 
	Sent: Thu 10/26/2006 9:53 PM 
	To: FDO Developers 
	Subject: [fdo-dev] GetProviderDatastoreType()

	I see there is a new manditory method for connection info classes called
	GetProviderDatastoreType() that can return one of:
	FdoProviderDatastoreType_Unknown, FdoProviderDatastoreType_File,
	FdoProviderDatastoreType_DatabaseServer, FdoProviderDatastoreType_WebServer
	It seems someone modified fdogdal to return FdoProviderDatastoreType_File,
	which is usually true.  But in some cases it is a web server, or another
	sort of virtual network service (ie. OGDI gltp).  And GDAL does not know
	which of these applies even for an active connection.
	Is the return result of this method important?  Is there any reason I
	shouldn't just return _Unknown since I don't really know?
	Best regards,
	I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
	light and sound - activate the windows | http://pobox.com/~warmerdam
	and watch the world go round - Rush    | President OSGeo, http://osgeo.org
	To unsubscribe, e-mail: dev-unsubscribe at fdo.osgeo.org
	For additional commands, e-mail: dev-help at fdo.osgeo.org

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

More information about the Fdo-internals mailing list