[mapguide-users] Oracle Spatial v/s Oracle Locator with MapGuide FDO

[Simon Greener]

Rob,

> The Oracle provider doesn't require the F_* tables to work with
> MapGuide.  It has some restriction if they are not present but the data
> should be readable in MapGuide through the provider.  The F_* are used
> to store the FDO metadata.  If these tables are not present, the FDO
> schema will be generated by reverse engineering the Oracle table
> definitions.
>
> If you have some use case that doesn't work, we certainly would like to
> know about it.

Always happy to admit when I am wrong.... We could not connect properly  
without the
tables using some straight C++. I can't remember the return code from the  
FDO interface
but when we created the tables the connection succeeded. Then we could not  
read any data
so we tried to create the "layer" definitions... we gave up. So, if there  
is a property
of the connection class we need to set to make it work with native OS  
table/columns as
recorded in *_SDO_GEOM_METADATA we are all ears! ;-) Some example C++ code  
might help!

regards
S
-- 
SpatialDB Advice, Solutions Architect, Manifold Enthusiast, Oracle Spatial  
Specialist.
Allens Rivulet, Tasmania, Australia.
Voice: +61 3 62396397
Longitude: 147.2048
Latitude: -43.0141