My Tafs are full of insert actions followed by @@IDENTITY gleaning result action, but these are wrapped into transaction actions. Up until reading this thread I thought that this setup is sufficient to get me the correct record identity. Should I change anything in my setup?
> -----Original Message----- > From: Scott Cadillac [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 01, 2002 12:36 AM > To: Multiple recipients of list witango-talk > Subject: Re: Witango-Talk: Identity after Insert > > > Thank you Klaus, for clearing that up in simple terms. > > Although I don't use @@IDENTITY very much, I find it a very > useful function > but I admit I've wondered about this point. I've read the SQL On-line > documentation, but frankly it didn't clarify things when I > tried to match up > SQL-Server's explanation of a Session and what we understand > is a Witango > Thread. > > Are they the same thing? My guess is that they are not - correct? > > Does a single SQL 'Session' count the same as a single SQL > 'Seat License'? > > Presumably a Session can contain multiple Threads, when hooked up to a > web-application like Witango? > > Although I primarily use SQL-Server for all my work, I freely > admit to being > more of an Application Programmer than a Database Programmer. > Once upon a > time I used to have a DBA on staff - but down-sizing has left > me as the sole > Developer here to cover all the bases. > > I know we've covered this topic in the past, but I could use > a refresher if > anyone has some comments. > > Thank you. Cheers... > > > Scott Cadillac > http://xml-extra.net > [EMAIL PROTECTED] > > > ----- Original Message ----- > From: "Klaus Sonnenleiter" <[EMAIL PROTECTED]> > To: "Multiple recipients of list witango-talk" > <[EMAIL PROTECTED]> > Sent: Tuesday, April 30, 2002 6:29 PM > Subject: Re: Witango-Talk: Identity after Insert > > > > Brad, > > > > Sounds like you're using either MS-SQL or Sybase. Either > way you don't > have > > to run a select after the insert. Both have a built-in variable for > > auto-increment fields (@@identity) and you can either > return it in your > > stored procedure or from the next Tango action. > > > > The only problem with doing this in a Tango action is that > there is no > real > > guarantee that you're seeing the correct identity field. > For example, if > you > > are using two consecutive Tango actions, you could run into > a situation > where > > two threads are doing an insert and the first one gets the > identity field > > only after the second insert - guess what you're getting > for @@identity? > > Yep... ;-) Remember, this has nothing to do with Tango - > there is only one > > identity variable and it will always be set ot the last > identity field > > inserted. > > > > Klaus > > > > On Tuesday 30 April 2002 08:37, Brad Robertson wrote: > > > I am currently using a Direct DBMS action in wTango that > calls a stored > > > procedure to insert a record and then return the new > identity of that > > > field, it seems that works better than a insert then > search action to > get > > > the identity field. I was wondering if 5.0 or later will have the > ability > > > to grab this field on insert, or if anybody has a less > tedious way of > doing > > > this... > > > > > > Brad > > > > ---------------------------------------- > > Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1" > > Content-Transfer-Encoding: quoted-printable > > Content-Description: > > ---------------------------------------- > > > ______________________________________________________________ > __________ > > TO UNSUBSCRIBE: send a plain text/US ASCII email to > [EMAIL PROTECTED] > > with unsubscribe witango-talk in the message body > > > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to > [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
