Cooper S ALL4. Congratulations on your new MINI. This Owner's Manual should be considered a permanent part of. The fastest way to find information on a particu- lar topic or item is by using the index, refer to page 260. Reporting safety defects. AT A GLANCE 9.

Caution mysql_insert_id() will convert the return type of the native MySQL C API function mysql_insert_id() to a type of long (named in PHP). If your AUTO_INCREMENT column has a column type of BIGINT (64 bits) the conversion may result in an incorrect value. Instead, use the internal MySQL SQL function LAST_INSERT_ID() in an SQL query.

For more information about PHP's maximum integer values, please see the documentation. Note: Because mysql_insert_id() acts on the last performed query, be sure to call mysql_insert_id() immediately after the query that generates the value. Note: The value of the MySQL SQL function LAST_INSERT_ID() always contains the most recently generated AUTO_INCREMENT value, and is not reset between queries. How to get ID of the last updated row in MySQL? 75 down vote I've found an answer to this problem:) by Pomyk SET @update_id:= 0; UPDATE some_table SET row = 'value', id = (SELECT @update_id:= id) WHERE some_other_row = 'blah' LIMIT 1; SELECT @update_id; EDIT by aefxx This technique can be further expanded to retrieve the ID of every row affected by an update statement: SET @uids:= null; UPDATE footable SET foo = 'bar' WHERE fooid >5 AND ( SELECT @uids:= CONCAT_WS(',', fooid, @uids) ); SELECT @uids; This will return a string with all the IDs concatenated by a colon. (questions: 1388025 form stackoverflow).

If you insert a data row by using the ON DUPLICATE KEY UPDATE clause in an INSERT-statement, the mysql_insert_id() function will return not the same results as if you directly use LAST_INSERT_ID() in MySQL. See the following example: mysql_insert_id: ', mysql_insert_id ();?>This will print: LAST_INSERT_ID: 1 mysql_insert_id: 1 In this case the function returns the same as the MySQL-Statement. But see the insert on an existing key: mysql_insert_id: ', mysql_insert_id ();?>This will print: LAST_INSERT_ID: 2 mysql_insert_id: 1 By using the ON DUPLICATE KEY UPDATE clause, only the old datarow will be modified, if the INSERT statement causes a duplicate entry, but the LAST_INSERT_ID() function returns the next auto_increment value for the primary key, which is by the way not set as the next auto_increment value in the database. The mysql_insert_id() function returns the primary key of the old (and changed) data row. For me this is the right operation method, because the LAST_INSERT_ID() function returns a value which is not referenced to a data row at all. Greets from Munich. There's nothing inherently wrong with using auto-increment fields.

There's also nothing wrong with the main competetive idea, which is for the database to supply a primitive sequence of non-repeating identifiers, typically integers. This is rather like which side of the road you drive on. The bigger problem is when people don't understand what they are doing with database access. It's like driving a car without really knowing the rules of the road.

Such people wind up making bad decisions without realizing it, and then, eventually, something breaks. Databases are complex beasts, and worth taking the time to really understand. Learn about the implications and limitations of different approaches to solving problems. Then, you will be prepared to pick a solution based on what has to work. I don't get all the fuss around this. I read: 'The value of mysql_insert_id() is affected only by statements issued within the current client connection. It is not affected by statements issued by other clients.'

See: I can't really see what's inaccurate about that. 'In the case of a multiple-row INSERT statement, mysql_insert_id() returns the first automatically generated AUTO_INCREMENT value; if no such value is generated, it returns the last last explicit value inserted into the AUTO_INCREMENT column.' I must be missing something here but why would you insert multiple rows and then only handle the last one with some favoured behaviour? You could just as well insert them one at a time and then handle each row separately with the latest id. I can't see what's wrong with that. However I can see what's wrong with simply using max(my_table.id_column) because of the concurrent access issues this would imply. And the primary reason to use neither of those last two solutions is both could result in race conditions when there is more than a single user with access to the database.

Aladdin Hasp Key Driver Windows 8. When you use MAX or ORDER BY DESC LIMIT 1 you will retrieve the maximum value from the table, at that moment. That doesn't mean another user doesn't do an insertion in the primary and secondary table BEFORE you do your insertion in the secondary table. You have thus inserted a row with a correct id into the second table. Always use last_insert_id(). Using 'SELECT MAX(id)+1.' Will not return the next auto_increment id. This function is totaly unreliable by two reasons.

In race conditions there is no guarantee that other user will not insert new record while your function have done its work. This will render your 'generated' last_id obsolete. It is rare case but it happens.

Most of all, if the last record(s) in the table is deleted the max id will no longer match the auto_increment value, because auto_increment never repeats numbers, it increases whenever an insert statement is completed and does not decrease if you erase the last record!!! If you have this table with the last record deleted: id name 1. Truck - [erased] auto_increment is 4 but MAX(id) is 2!!! As mentioned by frumler at the-beach dot no_spam dot net the LAST_INSERT_ID works like a charm when inserting values into tables. I'm not sure why anyone would need mysql_insert_id() when LAST_INSERT_ID is readily available. Example: Say you have a table called 'transaction' and a table called 'accounts'.

Obviously each account must be created using a transaction, so every time a record is created in the accounts table, a record must be created in the transaction table containing the same account_id(auto_increment) that was just created by mysql. Here's a simple way to do this. If you use this function after doing an INSERT. SELECT to insert multiple rows at once, you get the autonumber ID of the *first* row added by the INSERT.

If there are 4 records in table 'init' that have column 'type' = 2 I want to add these 4 records to table 'game' Table game has an autonumber column 'game_id' that is currently at 32. If I do this query: INSERT INTO game (type, players, rounds) SELECT type, players, rounds FROM init WHERE type = 2 Then mysql_insert_id() will return 33, not 36. I believe the 'resource link' being referred to is not what is returned from mysql_query() but the $link returned from mysql_connect().

Mysql_insert_id() will just use the most recent connection if there is no explicit $link being used. So the above example in the manual page itself should behave the same with mysql_insert_id($link) at the end instead of the mysql_insert_id() they used.

If you had multiple connections, the $link might come in handy. Also in reading the mysql manual itself, there is some enlightening information on the fact that this does appear to be totally safe to use because it is on a per-connection basis. Here's the relevant quote from the manual on LAST_INSERT_ID() which is located here: 'The last ID that was generated is maintained in the server on a per-connection basis.

This means the value the function returns to a given client is the most recent AUTO_INCREMENT value generated by that client. The value cannot be affected by other clients, even if they generate AUTO_INCREMENT values of their own. This behavior ensures that you can retrieve your own ID without concern for the activity of other clients, and without the need for locks or transactions.' Sounds safe to me.

I couldn't imagine this would be done any other way *but* on a per-connection basis, otherwise chaos would ensue. The only way to test it would be to perform a multi-thread type test. Perhaps someone is up for it and wants to post their results somewhere?:). Other methods seem to have problems with missing records in auto increment sometimes you will have records 1 2 5 6 most functions would return the value of 5 for next auto increment when indeed it would be 7. This is the only way I found to make this work so I can use my customer number and the record number to provide a truly unique customer number that is also useful. $next_increment = 0; $qShowStatus = 'SHOW TABLE STATUS LIKE 'your_table'; $qShowStatusResult = mysql_query($qShowStatus) or die(mysql_error()); $row = mysql_fetch_assoc($qShowStatusResult); $next_increment = $row['Auto_increment']; echo $next_increment; then you can do something like this echo $next_increment.'

Rand(); My first post: I hope this is useful to someone. Simon Aronson Stack Pdf Documents on this page. Be careful when using 'insert ignore'.

If the unique index already exists, the record will not be added, but it WILL give you the id of the next auto_increment value even though it didn't create it. '; echo mysql_insert_id ().

'; // same record, database is unique on 'num' $sql = 'insert ignore into sometable set num=10'; mysql_query ( $sql ) or die(); echo mysql_affected_rows (). '; echo mysql_insert_id ().

';?>would give: 1 116372 0 116373. If you want to use the ID that was generated for one table and insert it into a second table, you can use SQL statements like this: INSERT INTO foo (auto,text) VALUES(NULL,'text'); # generate ID by inserting NULL INSERT INTO foo2 (id,text) VALUES(LAST_INSERT_ID(),'text'); # use ID in second table.found here: It works even without inserting the NULL value for some reason;) The following is great for monitoring: $new_id = mysql_insert_id(); print 'New id: $new_id n'; Hope it helps you all, cheers.