Hi guys, I have the following problem. I have two tables: table1 has an id and a field called something like options_id. The second table is called 'options'. Now I have SQL statements that do the following when I want to create a new entry in table1: 1.) Insert data into options. 2.) Get the LAST_INSERT_ID 3.) Insert data into table1 and set options_id to the result of LAST_INSERT_ID All works fine, however in order to keep the tables clean Id like the entry in the options table to have the same id as the entry in table1. This is usually the case except if two requsts come simultaneously and one of the threads pauses right before step 3. I thought of locking the tables but that means no read access for all requests which is bad. Any ideas? -CProgrammer

This looks interesting. So basically this blocks oter threads from writing but everyone can read, during the transaction?
Also once Icall SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
Do I have to reset this mode back to normal somehow after COMMIT. Are there any side effects for other querys in this connection?

Perfect, many thanks!