[fdo-users] Is there a Feature class naming convention
orest.halustchak at autodesk.com
Tue Jan 22 11:00:53 EST 2008
I'm not sure why these providers would change the class names this way.
From FDO you can ask for class name and fully qualified class name separately so there should be no need to change the class name this way. Class name should come back as "MyFeatureClass" and fully qualified class name should come back as "MySchema:MyFeatureClass".
From: Bruno Scott
To: fdo-users at lists.osgeo.org
ReplyTo: FDO Users Mail List
Sent: Jan 22, 2008 10:33 AM
Subject: [fdo-users] Is there a Feature class naming convention
When we create a feature class, let say using the MySQL provider we give a
feature class name example: "MyFeatureClass"
and when we query it we use the same "MyFeatureClass"
This is fine...
With the PostGIS provider, we create the feature with a name like
but we query with a different name example "MySchema.MyFeatureClass"
We have this same problem with the King.Oracle provider
When you have an application that uses any FDO RDBMS provider, it makes
things very difficult to handle.
We need to hardcode
"if provider == PostGis" then
"if provider == KingOracle then
And it is a bit against the FDO philosophy, a single language to address the
same way any spatial database,file
It there a reason for that different naming?
View this message in context: http://www.nabble.com/Is-there-a-Feature-class-naming-convention-tp15021175s18162p15021175.html
Sent from the fdo-users mailing list archive at Nabble.com.
fdo-users mailing list
fdo-users at lists.osgeo.org
Sent from my BlackBerry Wireless Handheld
More information about the fdo-users