The sequence is ok to create a unique id except it doesn't prevent the
people importing from importing the same month 2x or more.
SKurosky wrote in message <20000208141651.01104.00001383_at_ng-fe1.aol.com>...
>>NOSPAM WROTE:
>
>>I am interested in opinions from this group on the following issue:
>>I am building a DB backend for some imported reports (coming from excel,
>>word and other places). The backend is Oracle 8.1.5.
>>
>>Since these reports were designed by non-programming professionals there
is
>>no unique id. I am importing (from CSV) into a table and herein lies the
>>catch. I need to make sure that the table doesn't get imported twice.
>>
>>I know that I can create an index of a bunch of columns and hope that they
>>are unique (fairly easy actually), but theoretically indexes shouldn't
>>really be used to enforce these rules. Anybody have a similar situation? I
>>guess I could use a trigger and populate an extra field and then make that
>>unique.
>>
>>I have a little time (unlike most projects lately) so I would rather do it
>>right!
>>
>>TIA.
>>
>>
>>How about using a sequence?
>Sandy
>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
Received on Wed Feb 09 2000 - 10:14:43 CST
