(ccing geoserver list, as people there probably care - try to send these
to the list in the future).
Seems to make sense to me, but I don't know about how to put it into
geoserver, or if we should. It would have to go in to geotools, which
does not support foreign keys yet. And if it is to support them then I
almost think that it should do more than just report their presence, it
should create features that actually represent the relationship, with
multiple attribute types and embedded features.
If you want the keyref in your schema, however, then you can simply
define your own schema.xml file. We went through great pains to ensure
that users like you for whom DescribeFeatureType generation was not
sufficient could define their own schemas and use those instead. So
just put the schema you want in that file (located in the featureType
folder, alongside info.xml), and geoserver should return that for its
Describe response instead of generating one for your.
Chris
----- Original Message -----
From: "Mehdi ESSID" <essid@anonymised.com>
To: "Chris Holmes" <cholmes@anonymised.com>
Sent: Thursday, May 13, 2004 8:52 PM
Subject: Re: Keys
To resume our problem :
let's two relational tables city(id, a,b,c) and road(id, cityid,
d,e,f) when
cityid refers to id of the table city.
the problem is that if we publish this database on a WFS server and
then we
ask for the schemas of this tables we will have a road feature and a
city
feature but we lost the relationship that connect the cityid attribute
to
the id attribute.
This property is very important for us because we work on data
integration.
for the representation of a foreign key in xml schema we use the
keyref
elemnt.
.......
<keyref name="RoadForeignKey" refer="CityKey">
.....Thanks
----- Original Message -----
From: "Chris Holmes" <cholmes@anonymised.com>
To: "Mehdi ESSID" <essid@anonymised.com>
Sent: Thursday, May 13, 2004 1:07 PM
Subject: Re: Keys> No, the notion of keys is not really extracted. A primary key will
be
> used as the FID, so it will actually not show up as an attribute.
> Eventually foriegn keys should be feature attributes (an attribute
that
> is actually a feature) or else multiple attributes, but that
capability
> has not been added yet. Do you have another notion of how you'd
like
> the key represented in the schema? The concept does not seem to
> tranlate super well, to me - what is a foriegn key in an XML Schema?
>
> Chris
>
> Quoting Mehdi ESSID <essid@anonymised.com>:
>
> > Hi,
> > I would like to ask you if the notion of keys (primary or foreign)
in
> > relational databases is extracted when we execute a
> > describefeaturetype
> > command.
> > I made tests and I dont see any where the representation of key
in
> > the xsd
> > schema (the file returned by the DescribeFeatureType command).
> > Thanks
> >
>
>
>
>
> ----------------------------------------------------------
> This mail sent through IMP: https://webmail.limegroup.com/
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/