Witango-Talk: Reliability of sequences in Witango 5

[Todd Trann]

Hello

Now that the Witango engine is fully threaded, I'm wondering if this is going to mess up any taf's that use a direct DBMS statement to fetch the primary key of a record that was just inserted? In Tango 2000, this worked OK, if you had tables with sequences on the primary key:

- insert a record with an insert action
- using direct DBMS, execute something like: "SELECT last_insert_id()"

However, can the following occur in Witango 5?

- thread #1 inserts a record that is assigned primary key of 1
- thread #2 inserts a record that is assigned primary key of 2 (and because of ODBC connection pooling, this thread is using the exact same ODBC connection that thread #1 did)
- thread #1 selects "last_insert_id()" and gets a value of "2"
- thread #2 selects "last_insert_id()" and gets a value of "2"

Can that happen? Or is there something that I'm missing from the big picture that stops this from happening?

Thanks,
Todd
--------------------------------------------------------------
Todd Trann, B.S.E.E., B.Sc. [EMAIL PROTECTED]
Programmer / Analyst ph (306) 966-2610
Student & Enrolment Services fax (306) 966-5092
University Of Saskatchewan http://www.usask.ca/sas/
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body