From: Michael S. <msa...@pc...> - 2004-06-10 19:19:58
|
Michael, All primary keys are generated using sequences from within the database. It's assumed in the design of GUS that a table, i.e. DOTS.NAFEATUREIMP will have a corresponding sequence, DOTS.NAFEATUREIMP_SQ. Careful note! In Oracle, sequences are completely orthogonal to tables-- there's nothing preventing one from using the nafeatureimp_sq sequence to generate an id for any other table. The object model uses the above assumption to automatically generate the proper id for a row. If data has been loaded outside of the object model, then it's possible that your sequences are out of sync with their corresponding table (although based on what Steve's said, I'm not implying that this is the case here). Anyway, most of this is just FYI... I'll try to add a Wiki page on this shortly. --Mike On Jun 10, 2004, at 2:04 PM, Michael Luchtan wrote: > I am under the impressions that ga (or perhaps somewhere > else) has an internal counter to deal with things like primary keys > like > algorithm_implementation_id or algorithm_invocation_id when inserting > new entries. |