Hi, some times ago I remember a discussion with Jody and Jesse about FID generation in datastore transactions (inserts) and the fact that we should wait after the end of transaction to check what FID has been assigned to new features.
This is troublesome both during interactive editing (uDig for example) but also for me now that I'm trying to implement WFS 1.1 idgen support in transactions.... So I'm wondering, is this really needed? keys in databases are generated as soon as you insert data (well, you may have prepared statementbatches, but you can always flush the batch before leaving the transaction to get the keys back), and in file based stores it's more or less the same. So yes, I guess I could go without fancy capabilities if at least I could have generated feature ids before saying the last word on the transaction destiny (so that, for example, I can make it fail if I notice user provided FIDs haven't been used in a idgen=UseExisting request, and new ones have been generated instead). Cheers Andrea ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
