Would this be a worthwhile enhancement request through U2UG? Are Ken and I the only ones whining about this:
From: [EMAIL PROTECTED] > Ideally of course, the ID would be allocated by the DBMS > transparently when the record is inserted into the file, but > neither U2 product supports that concept as far as I know I don't know why it isn't already there. > (perhaps you could use a trigger, but ...). hmmmm... > so the next best > would be simply to move the ID allocation to be the very last > step in the transaction. Process everything under a dummy > key, unless this new foreign key is needed to be stored in another file. > then when all is ready and complete, do the ID > allocation. If using explicit TRANSACTION boundaries then do > this as the last IO inside the transaction and the issue of > locks being held until the COMMIT/ROLLBACK should cease to be > significant. unless modular coding (which is generally a good idea) has these buried in external blackbox subroutines. cds ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
