On Tue, Jan 17, 2012 at 2:54 PM, danielsan <[email protected]> wrote:
> So,
>
> i found the thread you mentioned and as far as i understand to be able to
> do
> what i explained i should create a gt_pk_metadata_table in my postgre DB
> ,which i did, specifying the policy as assigned and checking the expose
> primary key in the store configuration of geoserver.
> Basically as explained here:
> http://docs.geoserver.org/stable/en/user/data/primarykey.html
>
> I have tried this and although the metadata table seems to be read (from
> what i can assume from the postgre query logs) and the policy is 'assigned'
> the id is still generated with some random value. Is there something i am
> missing?
>
As far as I remember it is mentioned in the thread that to make that work
some modifications to the WFS code would be needed, besides what you
already did.
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
