> Hi,
>
> I have seen two ways to generate unique IDs for new features. First one is
> based on using integer as ID, and inserting new feature begins with query
> "select max(ID) from table". New feature gets value max(ID)+1. Another, and
> pretty safe way is to configure database table to ta
Hi Paolo,
Thanks for continuing this very interesting discussion. You make a good
point about not knowing the ID when auto-increment is used to generate the
new key. The solution to this may be (after db inserts) to reissue the
spatial query that loaded the Features from the database in the fi
Stefan,
I can surely assist you with turning in the reports this summer. We'll
work it out.
SS
On Thu, Apr 2, 2009 at 1:58 PM, Stefan Steiniger wrote:
> So.. I requested now to be a mentor for OSGeo using the google SofC
> pages. I guess somebody at OSGeo will handle that?
>
> ... lets see what
> Hi Paolo,
>
> Thanks for continuing this very interesting discussion. You make a
> good point about not knowing the ID when auto-increment is used to
> generate the new key. The solution to this may be (after db inserts) to
> reissue the spatial query that loaded the Features from the dat
> ...but if you inserted more than one new Faeture, how do you know which
> is which??? You should have "another" key of some form, to match them.
Ah, but why do you care which is which? It is only necessary to reload the
Features.
Larry
>
> >
> > I haven't had any problem using auto-increment
Hi,
We play with WFS-T at work, where the mechanism of what really happens finally
is hidden behind datastore drivers of WFS server like Geoserver or others.
Anyhow, the problem is still the same than with direct connections to database.
For example this document is handling rather similar si
>
> ...but if you inserted more than one new Faeture, how do you know which
> is which??? You should have "another" key of some form, to match them.
>
>
> Ah, but why do you care which is which? It is only necessary to reload
> the Features.
Yes, true, you are right!!!
It should work,
> Hi,
>
> We play with WFS-T at work, where the mechanism of what really happens
> finally is hidden behind datastore drivers of WFS server like Geoserver or
> others. Anyhow, the problem is still the same than with direct connections
> to database. For example this document is handling rathe
