Hi,
I post another thread because my features are well inserted now, ie. their
primary key (a column called "id") is valued with the database sequence (not
with ID generated by geoserver). Altough I'm not sure why it's working now
(seems that moving all my feature tables to the "public" schema was very
profitable for me).
But... if i look into the Set returned by the featureStore.addFeatures(), I
can see a HashSet where the keys are the IDs (initialy?) generated by
geoserver, eg: newesig:esig_points.9223372036854775791 <= "new" + my
namespace for this feature + "." + an id based on a unknown sequence, but
not on my DB sequence!
So how could I do to retrieve the "real" FIDs, ie. the ones which are really
used (at the end) for the insertion and which are based on my database
sequence?
Another relative question: why a Set and not a List is returned? Ordering
seems very important since a features collection could have been inserted,
so the client should retrieve a collection of relative FIDs which should be
ordered in the same way than the feature collection was.
Thanks a lot,
Vincent.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
