[fdo-trac] #349: ODBC provider incorrectly read SQL Server views

[FDO]

#349: ODBC provider incorrectly read SQL Server views
----------------------------------+-----------------------------------------
 Reporter:  pierrega              |         Owner:  gregboone
     Type:  defect                |        Status:  new      
 Priority:  blocker               |     Milestone:           
Component:  ODBC Provider         |       Version:  3.3.0    
 Severity:  3                     |    Resolution:           
 Keywords:  odbc sql server view  |   External_id:           
----------------------------------+-----------------------------------------
Comment (by ksgeograf):

 You can select the primary key of an ODBC connection using Maestro:
 http://trac.osgeo.org/mapguide/wiki/maestro

 You can't select multiple columns as the primary key, but for this
 particular problem it may be a usable solution.

 You cannot autodetect a primary key on a view, because the view may come
 from two tables, each with a primary key. Choosing either or both keys as
 the view's primary key won't work in all cases. So for views you are
 forced to choose the primary key manually, until some DB guys make
 metadata on views describing keys.

 I agree with Jason, this is not really anything FDO can solve.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/349#comment:3>
FDO <http://fdo.osgeo.org/>
Feature Data Objects