php,mysqli, and last_insert_id()

using PHP 5, mysqli extension, and mysql 4.1.3:  according to the mysql documentation, last_insert_id returns the last autoincremented value from an insert OR update.  ...but, how would you get an update query to autoincrement?
When I set an autoincrement field to a number I created, insert_id() returns 0.

Q: I need to get an updated record's primary key without having to submit a subsequent SELECT statement.  Allowing two consecutive statements (UPDATE, then SELECT) might allow another UPDATE to occur (in a multiuser environment) before the Select statement could be called, returning the second record's primary key value instead.  ...and 'no', I don't know the PK value I just updated, because my statement was 'UPDATE PK SET PK = PK+1 WHERE 1 LIMIT 1'
Reason: I have a single field , single value  table I use to maintain a counter.
stevoliciousAsked:
Who is Participating?
 
pat5starCommented:
That I don't know. I never change the PK field of any of my tables. Without knowing what (or why) you're doing it this way it's hard to offer advice. I would think that adding another field to your table that you use as the id field might be easier to work with. That way you can use the PK as the identifier of which row you are working on while you manipulate the value of your id field.
0
 
pat5starCommented:
MySQL guarantees that it will return the correct PK value of an insert even if there are simultaneous inserts occurring. The only thing you have to be sure of is that you use the same connection to the database for both the insert and then the SELECT LAST_INSERT_ID(). So if you obtain a connection, insert some data and then query for the last insert id before closing that connection you will always get the correct PK.
0
 
stevoliciousAuthor Commented:
...but what if the last statement was an update that sets the PK field to PK+1 (not autoincremented, not an insert).  Is there an update statement that would autoincrement the PK?...and does last_insert_id() truly work with updates as mentioned in the documentation?
0
 
JakobACommented:
potentially an UPDATE command can affect any number of rows, it does not make sense to have a last_affected_id() function. (and no, last_insert_id() do not give a meaningfull value after UPDATE, I think the reference is to the ON DUPLICATE KEY option that can turn an insert into an update if nessesarry)

so do a select first finding the id of the row to be updated, then do the update.

regards JakobA
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.