Comments on: How to quickly wipe and recreate a db table that doesn’t have a migration http://nubyonrails.wordpress.com/2008/01/17/how-to-quickly-wipe-and-recreate-a-db-table-that-doesnt-have-a-migration/ Occasional adventures of a freelance Rails coder Thu, 10 Sep 2009 13:43:18 +0000 http://wordpress.com/ hourly 1 By: nubyonrails http://nubyonrails.wordpress.com/2008/01/17/how-to-quickly-wipe-and-recreate-a-db-table-that-doesnt-have-a-migration/#comment-1007 nubyonrails Mon, 06 Apr 2009 19:41:45 +0000 http://nubyonrails.wordpress.com/2008/01/17/how-to-quickly-wipe-and-recreate-a-db-table-that-doesnt-have-a-migration/#comment-1007 Sergio - that's a very handy thing to know, thanks a lot! Sergio – that’s a very handy thing to know, thanks a lot!

]]> By: Sergio Salvatore http://nubyonrails.wordpress.com/2008/01/17/how-to-quickly-wipe-and-recreate-a-db-table-that-doesnt-have-a-migration/#comment-1005 Sergio Salvatore Mon, 06 Apr 2009 18:33:06 +0000 http://nubyonrails.wordpress.com/2008/01/17/how-to-quickly-wipe-and-recreate-a-db-table-that-doesnt-have-a-migration/#comment-1005 Hi, If we're talking about MySQL, running "TRUNCATE TABLE [tableName]" will reset the auto increment counter. It's also significantly faster than "DELETE FROM TABLE [tableName]" (which you correctly stated will not reset the auto increment counter) when there are a lot of rows in the table because it basically deletes the files and creates new ones based on the schema. Hi,

If we’re talking about MySQL, running “TRUNCATE TABLE [tableName]” will reset the auto increment counter. It’s also significantly faster than “DELETE FROM TABLE [tableName]” (which you correctly stated will not reset the auto increment counter) when there are a lot of rows in the table because it basically deletes the files and creates new ones based on the schema.

]]>