Comments on: Pitfalls with MySQL and auto_increment http://techblog.tilllate.com/2008/04/13/pitfalls-with-mysql-and-auto_increment/ it and development at europe's leading clubbing community Fri, 25 Jul 2008 12:36:10 +0000 http://wordpress.org/?v=2.5.1 By: Leo Büttiker http://techblog.tilllate.com/2008/04/13/pitfalls-with-mysql-and-auto_increment/#comment-5056 Leo Büttiker Sun, 20 Apr 2008 18:16:15 +0000 http://techblog.tilllate.com/2008/04/13/pitfalls-with-mysql-and-auto_increment/#comment-5056 @patrice: well...erhmm... yes! @patrice: well…erhmm…
yes!

]]> By: patrice http://techblog.tilllate.com/2008/04/13/pitfalls-with-mysql-and-auto_increment/#comment-4984 patrice Sun, 13 Apr 2008 16:20:20 +0000 http://techblog.tilllate.com/2008/04/13/pitfalls-with-mysql-and-auto_increment/#comment-4984 Well the real SNAFU here was that all of this was done on your production database, wasn't it? Well the real SNAFU here was that all of this was done on your production database, wasn’t it?

]]> By: Leo Büttiker http://techblog.tilllate.com/2008/04/13/pitfalls-with-mysql-and-auto_increment/#comment-4982 Leo Büttiker Sun, 13 Apr 2008 11:01:32 +0000 http://techblog.tilllate.com/2008/04/13/pitfalls-with-mysql-and-auto_increment/#comment-4982 Just for the information of our readers: Deleting the too high values and Alter table should be done while holding a lock on the table, to not get into troubles again. A lot of databases do not even have autoincrement (as postgresql) they use sequences for that. You can build this feature with a trigger in mysql as Peter describes <a href="http://www.mysqlperformanceblog.com/2008/04/02/stored-function-to-generate-sequences/" rel="nofollow">here</a>. Just for the information of our readers: Deleting the too high values and Alter table should be done while holding a lock on the table, to not get into troubles again.

A lot of databases do not even have autoincrement (as postgresql) they use sequences for that. You can build this feature with a trigger in mysql as Peter describes here.

]]>