From: Anjo K. <an...@kr...> - 2009-07-25 20:20:17
|
Am 25.07.2009 um 19:49 schrieb Chuck Hill: > Identify problem and fix seems like a better solution. And not all > database use the eo_pk_table, so this only addresses the problem for a > few. Oracle, FrontBase, Postgres etc. use database sequences. It is > probably just as common for someone to update the database and the > related sequence. Except... that you could create the pk with a restriction to either call a stored proc or update the sequence, so no harm done when someone enters data without updating the pk table? Cheers, Anjo |