|
hello, weve been having a really hard to track
error and i was wondering about something.
We have a table w/ an integer ID that is marked as
must be unique.
In our code, we do this to get the next
id:
select max(ID)+1 from table
and then in the very next action, its a DBMS using
the results of that select to insert into the table.
Well the error we are having is that fairly rarely,
the insert DBMS will fail saying rows must be unique (and the ID is the
only column marked as needing to be unique).
Could this be due to the multitasking nature of
witango where multiple people would hit the select code and get the
same ID before it does the insert?
Or does it finish one person's request completely
before moving to the next request?
Anyone had any problems like this before or know
how to get around it?
Thanks!
Atrix
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf |
- RE: Witango-Talk: a question Atrix Wolfe
- RE: Witango-Talk: a question Ben Johansen
- Re: Witango-Talk: a question Atrix Wolfe
- RE: Witango-Talk: a question Ben Johansen
- Re: Witango-Talk: a question Atrix Wolfe
- Re: Witango-Talk: a question Dan Stein
- RE: Witango-Talk: a question Ben Johansen
- Re: Witango-Talk: a question Dan Stein
- RE: Witango-Talk: a question Ben Johansen
- Re: Witango-Talk: a question Dan Stein
- Re: Witango-Talk: a question Robert Garcia
