Interesting. This is another good argument for using a key table guys.
Anyway, run the Oracle stored procedure to generate a number, then check for
the existence of that number in the primary key field in the table you want
to insert into. If the number exists, generate another number and repeat
the loop infinitely until you get an open key.
---mark
------------------------------------
Mark Warrick - Fusioneers.com
Personal Email: [EMAIL PROTECTED]
Business Email: [EMAIL PROTECTED]
Phone: 714-547-5386
Efax: 801-730-7289
Personal URL: http://www.warrick.net
Business URL: http://www.fusioneers.com
ICQ: 125160 / AIM: markwarric
====================================
> -----Original Message-----
> From: Mike Amburn [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 26, 2001 12:10 PM
> To: CF-Talk
> Subject: oracle long table corrupts itself... ideas?
>
>
> (Diagnostic Data: using Oracle 8i, ColdFusion 4.51 SP2, Oracle native
> drivers)
>
> I have a table where I store user session information. At some point
> over time, the index corrupts itself and i begin to get foreign key
> constraints because it'll attempt to insert a row using a key ID that
> has already been used. Ironically, it is also the only table in the
> database that includes a field of the data type "long".
>
> Is that just a coincidence or could there be a correlation? If not, what
> else could be corrupting my index? or is it something other than my
> index?
>
> any help is greatly appreciated!
> -mike
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
