Schema's are generated now, so the bug could be closed. I have some tiny
remarks/questions though. In the generated schema the geometry is of type
gml:GeometryAssociationType. Isn't it necessary to specifiy what kind of
geometry it is, e.g. gml:LineStringPropertyType?
Yeah, I'm not sure, this is definitely a bit of hack so it doesn't just
fail. It comes down to the problem that oracle will put two different
types in a spatial column, so that we can't say for sure that the column
is definitely all linestrings (Sean, correct me if I'm wrong here).
Maybe we could do our traditional half-hack of user configuration?
And it would be nice if in
some future version of GeoServer (more) restrictions on the attributes (e.g.
maxlength) could be detected and put in the schema. Because for instance,
when such a restriction is not met, an insert will fail. So for the
application I'm working on I'll still use self-defined schema's.
Yes, future versions should _definitely_ put on more restrictions. This
is just a first stab. That's why the schema.xml will continue to be a
part of things, as many users will certainly want more control. Hopefully
that need will decrease as geotools gets better, but I doubt it can be
entirely eliminated.
Chris
Anyway,
thanks for the fix!
Thijs> -----Original Message-----
> From: Chris Holmes [mailto:cholmes@anonymised.com]
> Sent: Friday, January 09, 2004 5:23 PM
> To: Thijs Brentjens
> Subject: Could you try out this for gml?
>
>
> I'm hoping it'll fix the geometry problem. Let me know if it works and
> I'll close the bug.
>
--