the already implemented solution is : select ... for update; a unique key gives you an error that you have to manage for updating rather than insert. you must catch and analyse that the error is "duplicate key" and not another.
but this is right if you want lauch insert without waiting to see if there is a duplicate key error. Mathias Selon Kevin Burton <[EMAIL PROTECTED]>: > I've been thinking about this for a while now. > > If you have an app that can compute a unique key (hashcode) and you have > a unique index it should be possible to just do an INSERT instead of a > SELECT first to see if the record doesn't exist and then an INSERT. > > This should be 2x faster than the SELECT/INSERT combo right? > > -- > > > Use Rojo (RSS/Atom aggregator)! - visit http://rojo.com. > See irc.freenode.net #rojo if you want to chat. > > Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html > > Kevin A. Burton, Location - San Francisco, CA > AIM/YIM - sfburtonator, Web - http://peerfear.org/ > GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412 > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
