TopLink can take advantage of automaticcally created IDs, for example by
using "SELECT @@identity" after an INSERT. Unfortunately this means having a
second SQL command forwarded to the server after each INSERT (including parsing
JDBC has explicit support for getting created keys: Statement.getGeneratedKeys
() will return a ResultSet with all automatically generated keys. It would be
great, if a future verson of TopLink would allow a driver to decide whether the
current solution is used (subsequent SELECT) or the JDBC method is used (which
might be faster, but is not supported with all platforms).