you get the last insert id based on your connection, and concurrent operations will have different connections, so the case of mixed up keys wont happen. A more real concern though would be if your insert fails, this would mean that getting the last id would fetch the last successful insert on that connection and use it<br>
<br><div class="gmail_quote">On Wed, Jan 19, 2011 at 3:05 PM, James Nzomo <span dir="ltr">&lt;<a href="mailto:kazikubwa@gmail.com">kazikubwa@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Locking may be a good option but the performance to integrity tradeoff .....<br>Locking might also frustrate users when trying to insert<br><br>Anyway, I think i&#39;ll use a different way of getting the primary key other than relying on the last insert<br>


Or maybe employ the use of a surrogate key<br><br>I&#39;ll research on the matter then share the best solution in my view<br>
<br>_______________________________________________<br>
Skunkworks mailing list<br>
<a href="mailto:Skunkworks@lists.my.co.ke">Skunkworks@lists.my.co.ke</a><br>
<a href="http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks" target="_blank">http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks</a><br>
------------<br>
Skunkworks Rules<br>
<a href="http://my.co.ke/phpbb/viewtopic.php?f=24&amp;t=94" target="_blank">http://my.co.ke/phpbb/viewtopic.php?f=24&amp;t=94</a><br>
------------<br>
Other services @ <a href="http://my.co.ke" target="_blank">http://my.co.ke</a><br></blockquote></div><br>