|
From: Thomas R. <tri...@tr...> - 2003-05-03 15:35:55
|
Jean-Pierre, Thanks for your changes. I think adding long as a return value has been planned, but it was never implemented. Isabelle, do you you want to make these changes or do you want me to do it? I'm modifying a few other jdbc classes this weekend, so I don't mind adding these changes as well. For key generation support I think we should provide support for the following: 1. Sequences - like the OracleSequenceMaxValueIncrementer. Do we need something for Postgres and DB2? 2. Identity/Autoincrement - a "sequence" table where we use some sql to increment and retrieve the next value. This is implemented in MySQLMaxValueIncrementer. Do we need implementations for HSQL, MS SQL Server, DB2 and Sybase? 3. Stored Procedure = a procedure that wraps access to a Sequence, Identity/Autoincrement or any other proprietary database key generation facility. I'll look into providing an implementation for this. I think we should discourage use of "select max(id) + 1" type of solutions and therefore we should remove the RdbmsMaxValueIncrementer. We can leave this type of implementation up to the individual developer. Thomas > This is a multi-part message in MIME format. > > > Hi Isabelle, > > Related on my last post on the Spring Framework list, I enclosed my > proposals of changes to handle long keys on databases. > As I'm not registered as developer, I cannot upload. And in all cases, > it's your work, so your approval is also mandatory. > > NB: It's nothing about caching in this proposal. > > Best regards, > Jean-Pierre PAWLAK > jp....@ti... > |