[fdo-users] FDO OSGeo for ODBC
gavin.cramer at autodesk.com
Wed Jun 11 12:03:17 EDT 2008
Yes, it does look for views. Does the view lack a primary key? The FDO ODBC Provider has a number of ways to find identifier properties, with the main one being primary keys. After that there are a number of fallbacks, with the last one being to grab any non-NULLable columns and treat them as identifier properties. There has been discussion in the past of removing this last fallback, but it has not happened yet. In the meantime, if the view can be given a primary key (anything expressly denoted as such, or anything that is autogenerated), ODBC Provider will use it instead of the columns that you want for ordinates.
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Pierre Gauthier
Sent: Tuesday, June 10, 2008 11:54 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] FDO OSGeo for ODBC
I'm using the FDO ODBC provider with MapGuide Studio 2009 to connect to a SQLServer database and I wonder if views are supported when generating the list of tables.
The problem I have is that if my view is created from a table where my X and Y columns does not allow nulls, MapGuide Studio list my X and Y columns in the view as if they are key fields and I can`t select them as X and Y.
I found a way to workaround this problem by using the mapagent and editing the xml but this is a bit annoying for myself and I can imagine how it can be for my customer.
Anybody else has seen this issue?
Analyste programmeur sénior
pierrega at consortech.com<mailto:pierrega at consortech.com>
Solutions Consortech inc.
Tél: 450-676-1555 x217
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fdo-users