[mapguide-users] RE: Incorrect key fields when using views/queries inMGOS 1.2 RC1

[Ismael Cams]

Hello Dave,

no there are no composite keys defined. There is only one single primary key
(id).

I have checked the schema but all fields are available, so this seems to be
ok. What I noticed is that the properties are showed when trying to select a
feature, but the selection is not highlighted. When I remove the "extra" key
fields from the view selection works as expected. 

Regards,
Ismael



Are any of the keys you are using composite keys (not single columns)?

A more likely possibility is a column data type that the system doesn't like
is preventing the selection from working.

Save your connection using the view with all the columns you require.

Then from http://localhost/mapguide/mapagent/index.html select Feature
Service and attempt a Describe Schema. You need to enter your path to your
resource. You can do an Enumerate Resources under Resource Services to get
the path if you are unsure. If any columns are missing then it may be a data
type issue.

Regards,
Dave

-----Original Message-----
From: mapguide2007 at gmail.com [mailto:mapguide2007 at gmail.com]
Sent: Friday, June 15, 2007 1:39 AM
To: Dave Wilson
Subject: RE: Incorrect key fields when using views/queries inMGOS 1.2 RC1

Hello Dave,

some extra information:

the key fields seem not to be generated randomly after all. Instead all
fields that are indicated as required in Access are used. For tables where
there are no required fields I can choose the key fields as expected.



Dave Wilson-3 wrote:
> 
> Can I assume you are using ODBC?
> 
> The key column is in a drop down and you specify it. The "random" selected
> columns are likely float/decimal columns that are being defaulted as
> candidates for X,Y,Z geometry columns. These aren't required if you aren't
> attempting to display point geometries. Don't select the Geometry checkbox
> unless you plan to create a point geometry layer.
> 
> Regards,
> Dave
> 
> -----Original Message-----
> From: mapguide-users-bounces at lists.osgeo.org
> [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Ismael Cams
> Sent: Thursday, June 14, 2007 8:38 AM
> To: mapguide-users at lists.osgeo.org
> Subject: [mapguide-users] Incorrect key fields when using views/queries
> inMGOS 1.2 RC1
> 
> 
> Hello,
> 
> is there any possibility to change the key fields for views/queries. I
> have
> an query in Access on a table where I have defined a primary key. But when
> creating a data source MapGuide seems to choose some random fields for the
> key which I can not adapt. 
> I suspect that this behaviour is the reason why I can not select any
> feature
> (although they are displayed correctly).
> 
> Thanks in advance.
> 
> Ismaël
> -- 
> View this message in context:
> http://www.nabble.com/Incorrect-key-fields-when-using-views-queries-in-MGOS-1.2-RC1-tf3922083s16610.html#a11121303
> Sent from the MapGuide Users mailing list archive at Nabble.com.
> 
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
> 
> 
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
> 
> 

-- 
View this message in context: http://www.nabble.com/Incorrect-key-fields-when-using-views-queries-in-MGOS-1.2-RC1-tf3922083s16610.html#a11189236
Sent from the MapGuide Users mailing list archive at Nabble.com.