http://www.khankennels.com/blog/index.php/archives/2010/01/13/which-way-to-go-which-way-to-go/ Lig's accidentally overheard ramblings on MySQL/PHP and life in general Wed, 26 May 2010 18:31:19 +0000 hourly 1 http://wordpress.org/?v=3.0.1 http://www.khankennels.com/blog/index.php/archives/2010/01/13/which-way-to-go-which-way-to-go/comment-page-1/#comment-840434 Brad Wed, 13 Jan 2010 15:11:20 +0000 http://www.khankennels.com/blog/?p=672#comment-840434 I agree, the CREATE TABLE LIKE seems to be the better way to go. It seems that it would be less of a maintenance problem as well. You won't need to change the query if the Indexes change. I agree, the CREATE TABLE LIKE seems to be the better way to go. It seems that it would be less of a maintenance problem as well. You won’t need to change the query if the Indexes change.

]]> http://www.khankennels.com/blog/index.php/archives/2010/01/13/which-way-to-go-which-way-to-go/comment-page-1/#comment-840433 Timothy Wed, 13 Jan 2010 03:44:45 +0000 http://www.khankennels.com/blog/?p=672#comment-840433 I think this is a good question. With no eloquent answer, it gives your brain something to chew on. Personally, I like CREATE TABLE LIKE. It seems less error prone, having MySQL copy over the indexes rather than having me re-type them all. And two smaller queries (instead of one giant CREATE TABLE SELECT with index definitions) would probably be easier for others to understand after I'm gone. I think this is a good question. With no eloquent answer, it gives your brain something to chew on. Personally, I like CREATE TABLE LIKE. It seems less error prone, having MySQL copy over the indexes rather than having me re-type them all. And two smaller queries (instead of one giant CREATE TABLE SELECT with index definitions) would probably be easier for others to understand after I’m gone.

]]>