× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Nope. The function will return (baring bugs <G>) the value of the last
insert _YOU_ did. It doesn't care about triggers or other jobs. 

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
 

-----Original Message-----
From: Metz, Zak [mailto:Zak_Metz@xxxxxx] 
Sent: Monday, August 11, 2003 2:09 PM
To: Midrange Systems Technical Discussion
Subject: But what key? (was RE: Row locks in DB2/400 UDB)


I don't see how this helps. It's still a separate statement, so
additional inserts could have occurred in-between, and if I put it in
the Insert statement it gives me the last value inserted, not the one
currently being inserted. Doesn't seem "industrial strength," much like
a Select max()+1, then Insert. I hope I'm just missing something here.
Alas, my box doesn't run v5r2 anyway.

> -----Original Message-----
> From: Walden H. Leverich III
> Sent: Monday, August 11, 2003 1:43 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Row locks in DB2/400 UDB
> 
> 
> Zak, 
> 
> Not true. See IDENTITY_VAL_LOCAL() at
> http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm?in
> fo/db2/rbafzms
> tscale.htm
 
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.