Hi Jukka, thanks a lot for this information, it was exactly what I needed! It works now!
I think I confused Primary Key Constraint (which wrongly inserted into gt_pk_metadata_table) with the column that should SERVE as primary key. Thanks! Barbara Rahkonen Jukka wrote: > > Hi, > > Metadata record must suit your your data source and in your case it is the > view. Information needed: > > - schema of the view > - name of the view > - column in the view that should be used as primary key > - in case of multi-column primary keys, index of first primary key part, > and then again the column and index for the next part > - pk_policy and pk_sequence are needed only with WFS-T so you can left > them null > > Primary key columns will be eaten out from the output. If you need to get > the information of the primary key columns into output you can select it > twise into the view > > create view view_name as (select primary_key PK, primary_key > to_be_published, second_column, ....) > > -Jukka Rahkonen- > -- View this message in context: http://old.nabble.com/postgresql-postgis-views-and-primary-keys-tp28616028p29621032.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
