Paul
Sorry I wasn't quite clear I meant @@Identity
ie
If the statement fires one or more triggers that perform inserts that
generate identity values, calling @@IDENTITY immediately after the statement
returns the last identity value generated by the triggers.
And as I understand it is only guaranteed per connection so connection
pooling can stuff it up (under heavy loads)
Neven
----- Original Message -----
From: Paul Ritchie <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Sent: Thursday, 11 January 2001 18:04
Subject: RE: RE: [DUG]: [DUG-DB]: Unique IDs
> Neven,
>
> Well you learn something new every day eh?
>
> > a/ They are only unique to a connection and
>
> I didn't think so. Aren't they generated from within the database? I use
> them in stored procedures and I don't see how they could be only unique to
a
> connection. Can you point me to documentation to that effect?
>
> > b/ They are only held for the last action.
>
> So is the current value of a generator. Isn't that the same thing?
>
> Paul.
> --------------------------------------------------------------------------
-
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
> To UnSub, send email to: [EMAIL PROTECTED]
> with body of "unsubscribe delphi"
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
