Lance has been investigating the autogenerated keys questions for us
with the EG. They aren't done yet, but here is what they have so far.
Lance said it was ok to forward their progress to the list.
Kathey
--- Begin Message ---
Hi Kathey,
I have not completely closed on this with the EG, but am close. Here is
where I am (a snipped from a summary to the EG):
1. null should not be returned at all from getAutoGeneratedKeys as the
javadocs are clear an Empty ResultSet should be returned
2. javadocs are clear that if the values passed as a column name are not
valid column names a SQLException should be thrown, this would include
Null and an Empty Array, Empy String being specified
3. Statement.NO_GENERATED_KEYS should result in an Empty ResultSet being
returned even if keys are generated by the Statement
4. Everyone so far appears to return a key if: the column is valid but
is not an auto key column (example identity) or the column specified is
a SEQUENCE
We do need at least 1 new metadata method but i think it needs to have
its wording changed to:
boolean generatedKeyAlwaysReturned() - indicates that a generated key
will always be returned if the columns specified for the auto generated
key columns are valid and the statement succeeds. The key that is
returned may or may not be based on the columns for the auto generated
key columns. Consult your JDBC driver documentation for additional details.
Kathey Marsden wrote:
Hi Lance,
It looks like there will be a second release candidate for 10.5, so if
possible I would like to try to get the correct behavior implemented
for Derby. Is there any chance we will know something this week?
Thanks
Kathey
--- End Message ---
