I’ve got my database set up with three tables – code, tags, and code_tags for tagging posts.
This will be the SQL query processed when a post is submitted. Each tag is sliced up by PHP and individually inserted using these queries.
INSERT IGNORE INTO tags (tag) VALUES ('$tags[1]');
SELECT tags.id FROM tags WHERE tag = '$tags[1]' ORDER BY id DESC LIMIT 1;
INSERT INTO code_tags (code_id, tag_id) VALUES ($codeid, WHAT_GOES_HERE?)
The WHAT_GOES_HERE? value at the end is what I need to know. It needs to be the ID of the tag that the second query fetched. How can I put that ID into the third query?
I hope I explained that correctly. I’ll rephrase if necessary.
Edit: Thanks for your help so far but I’m still struggling a bit in regards to what was pointed out – if it’s already there I can’t get the inserted ID…?
If you use
INSERT IGNOREand a new record is ignored (because of a unique key violation) mysql_insert_id() and LAST_INSERT_ID() don’t have a meaningful value.But you can use INSERT … ON DUPLICATE KEY UPDATE and LAST_INSERT_ID(expr) to set the data you expect LAST_INSERT_ID() to return in case of a doublet.
Step-by-step:
Let’s assume you have a table
tagslikeInserting a tag twice results in a
duplicate keyviolation because ofunique key(tag). That’s probably the reason why you’ve usedINSERT IGNORE. In that case MySQL ignores the violation but the new record is ignored as well. The problem is that you want the id of the record having tag=’xyz’ regardless of whether it has been newly created or it was already in the database. But right now mysql_insert_id()/LAST_INSERT_ID() can oly provide the id of a new record, not an ignored one.With
INSERT ...ON DUPLICATEyou can react on such duplicate key violations. If the new record can be inserted (no violation) it behaves like a “normal” INSERT. But in case of a duplicate key violation the part after ON DUPLICATE KEY is executed like an UPDATE statement for the record with that particular index value already existing in the table. E.g. (with an empty tabletags)This will simply insert the record as if there was no ON DUPLICATE … clause. id gets the next auto-increment value, dummy the default value of 0 and tag=’tag A’. Let’s assume the newly create auto_increment value was 1. The resulting record stored in MySQL is (id=1, tag=’tag A’, dummy=0) and LAST_INSERT_ID() will return 1 right after this query. So far so good.
Now if you insert the same record again with the same query a violation occurs because of the first record (id=1, ‘tag=tag A’, dummy=0). For this already exisitng record the UPDATE statement after ON DUPLICATE KEY is executed, i.e. the record becomes (id=1, tag=’tag A’, dummy=1). But since no new record has been created there was also no new auto_increment value and LAST_INSERT_ID() becomes meaningless. So still the same problem as with INSERT IGNORE.
But there is a “special” construct that allows you to set the value LAST_INSERT_ID() is supposed to return after the ON DUPLICATE KEY UPDATE statement has been executed.
Looks strange but it really only sets the value LAST_INSERT_ID() will return.
If you use the statement
LAST_INSERT_ID() will always return the id of the record having tag=’xyz’ no matter if it was added by the INSERT part or “updated” by the ON DUPLICATE KEY part.
I.e. if your next query is
the tags.id for the tag ‘xyz’ is used.
The self-contained example script uses PDO and prepared statements. It should do more or less what you want to achieve.
prints
edit2: In case the PDO-part of the script and the prepared statements are intimidating, here’s the same thing using the old php-mysql module. But I urge you to use parametrized prepared statements. Doesn’t have to be PDO but I happen to like it. E.g. the mysqli module provides prepared statements as well, the old mysql module doesn’t.