on 1/28/03 11:42 AM, John W. Holmes at [EMAIL PROTECTED] wrote:
The reason I ask is, if you use mysql_insert_id() on a busy server and
it
does not function on a per-connection basis, don't you run the risk of
getting the last ID of somebody else's INSERT query on the server?
Yes, they are
-Original Message-
From: Randy Phillips [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003 9:30 AM
To: [EMAIL PROTECTED]
Subject: Re: [PHP-DB] mysql_insert_id() vs. last_insert_id()
on 1/28/03 11:42 AM, John W. Holmes at [EMAIL PROTECTED] wrote:
The reason I ask
Hi
I've been checking the last_insert_id() function out and I am curious. The
MySQL docs say to use the mysql_insert_id() function after an insert into
query to grab the key value. Both seem to work; however, there are some
subtle differences.
Which is the best one to use after a single insert
I've been checking the last_insert_id() function out and I am curious. The
MySQL docs say to use the mysql_insert_id() function after an insert
into
query to grab the key value. Both seem to work; however, there are some
subtle differences.
Which is the best one to use after a single insert
-
From: 1LT John W. Holmes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 11:37 AM
To: Randy Phillips; [EMAIL PROTECTED]
Subject: Re: [PHP-DB] mysql_insert_id() vs. last_insert_id()
I've been checking the last_insert_id() function out and I
am curious. The
MySQL docs say
So I read this thread and the MySQL doc on mysql_insert_id() and still
have
a related question.
Does mysql_insert_id() function on a per-connection basis? I read the
stuff
on last_insert_id() and it specifically mentions that the last ID is
stored
on the server on a per-connection basis.
