Gleb Paharenko wrote:
> Really, in my opinion, it contradicts with the manual. Please, send me
> the bug id in case you'll report the bug.
It turns out that it was reported nearly a year ago:
http://bugs.mysql.com/bug.php?id=6880
Björn Persson
--
MySQL General Mailing List
For list archives: htt
[mailto:[EMAIL PROTECTED]
Sent: Thursday, 17 November 2005 4:42 AM
To: mysql@lists.mysql.com
Subject: RE: Database IDs
Logan, David (SST - Adelaide):
> It looks like the LAST_INSERT_ID() is returning the id of the last
> auto_increment INSERT, this seems to be in line with the documen
5000
Australia
+61 8 8408 4273 - Work
+61 417 268 665 - Mobile
+61 8 8408 4259 - Fax
-Original Message-
From: Björn Persson [mailto:[EMAIL PROTECTED]
Sent: Thursday, 17 November 2005 4:42 AM
To: mysql@lists.mysql.com
Subject: RE: Database IDs
Logan, David (SST - Adelaide):
> It lo
Logan, David (SST - Adelaide):
> It looks like the LAST_INSERT_ID() is returning the id of the last
> auto_increment INSERT, this seems to be in line with the documentation.
>
>
>
> The ID that was generated is maintained in the server on a per-connection
> basis. This means that the value which t
Hello.
Really, in my opinion, it contradicts with the manual. Please, send me
the bug id in case you'll report the bug.
Björn Persson wrote:
> Gleb Paharenko:
>
>>Could you provide a repeatable test case for you problem?
>
>
> I don't know how repeatable this is. As I said I have
Björn Persson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 16 November 2005 10:06 AM
To: mysql@lists.mysql.com
Subject: Re: Database IDs
Gleb Paharenko:
> Could you provide a repeatable test case for you problem?
I don't know how repeatable this is. As I said I have one computer where it
Gleb Paharenko:
> Could you provide a repeatable test case for you problem?
I don't know how repeatable this is. As I said I have one computer where it
seems to work sometimes, as if there's a race condition. Right now it seems
repeatable on the computer I'm using at the moment:
mysql> select
Hello.
> I suppose I should file a bug report then?
Could you provide a repeatable test case for you problem?
If you're using LAST_INSERT_ID() in a wrong way, that doesn't
mean that there is something wrong with MySQL.
Björn Persson wrote:
> Gleb Paharenko:
>
>>So in you query both
Gleb Paharenko:
> So in you query both last_insert_id() should return the same value,
> which equals to the value that was set for an AUTO_INCREMENT column by
> the last INSERT or UPDATE query. Note that you have one query, which
> just inserts several rows, so during it is processed the returned v
Hello.
In the manual we have:
" Returns the first automatically generated value that was set for an
AUTO_INCREMENT column by the last INSERT or UPDATE query to affect such
a column."
So in you query both last_insert_id() should return the same value,
which equals to the value that was s
[EMAIL PROTECTED]:
> Robert Crowell <[EMAIL PROTECTED]> wrote on 11/11/2005 12:39:37 AM:
> > If I am relying on MySQL's AUTO_INCREMENT feature for the id for a
> table,how
> > can I reliably retrieve the ID of an item I just entered into the
> database?
> TFM is your friend. What you are looking
Robert Crowell <[EMAIL PROTECTED]> wrote on 11/11/2005 12:39:37 AM:
>
> Hello,
>
> If I am relying on MySQL's AUTO_INCREMENT feature for the id for a
table, how
> can I reliably retrieve the ID of an item I just entered into the
database?
>
> For instance, I have a table that stores first nam
Hi Robert,
You can use the function LAST_INSERT_ID() after the insert, this will
return the id that was just assigned.
It is documented here :
http://dev.mysql.com/doc/refman/5.0/en/information-functions.html
Regards
David Logan
Database Administrator
HP Managed Services
148 Frome Street,
Ade
13 matches
Mail list logo
