[Geoserver-users] Id generation with WFS 1.0

GeoServer GeoServer User
1

Hi Vincent,

Looking into the matter here is what I have come up with. In your table, if you have a primary key set then GeoServer should use those id's for fids when it generates features.

If you have a sequence which generated values for the primary key, then it should also use that when generating new fids, for say an insert.

This is venturing into a realm where i am not 100% certain if your version of GeoServer will actually behave like this. So I am bringing this conversation to the user list.

-Justin

GeoServer is the latest stable (1.4.0).

Could you just confirm me that there's no special conf to perform in order to force GeoServer/GeoTools to use existing database sequence? The primary key _must_ be called "fid" or it should work whatever its name?

In fact I don't guess how GeoServer (or GeoTools) is able to scan DB schema to detect which field is the primary key.. and which default value is associated with it. It sounds magic for me.

Vincent.

!DSPAM:1004,45ca2b9535767785049143!

--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org

2

Justin Deoliveira ha scritto:

Hi Vincent,

Could you just confirm me that there's no special conf to perform in order to force GeoServer/GeoTools to use existing database sequence? The primary key _must_ be called "fid" or it should work whatever its name?

In fact I don't guess how GeoServer (or GeoTools) is able to scan DB schema to detect which field is the primary key.. and which default value is associated with it. It sounds magic for me.

Ha ha :slight_smile: No, that's not magic, it's the JDBC standard.
Every database must provide a DatabaseMetadata object we can query to gather the structure of the database, be it table, primary key, foreign keys, indexes and the like. Spotting sequences is database dependent, each datastore does it in a different way.

Cheers
Andrea