Also:
ALTER TABLE TableName MODIFY COLUMN ColumnNameToMove longtext BEFORE
ColumnNameToPutBefore
ALTER TABLE TableName MODIFY COLUMN ColumnNameToMove longtext FIRST
ALTER TABLE TableName MODIFY COLUMN ColumnNameToMove longtext LAST
will work, depending on what you're looking to do.
sk
--
MySQL
ALTER TABLE TableName MODIFY COLUMN ColumnNameToMove longtext AFTER
ColumnNameToPutAfter
Note that long text is required (put in the correct column type you
intend to move)
Alternate:
INSERT INTO new_table SELECT columns-in-new-order FROM old_table;
DROP table old_table;
ALTER TABLE new_table RE
Hi.
For what I know, MySQL always reads a whole row if it has to read the
row at all. So, no, column order should not matter at all.
With MyISAM tables, indexes are in a seperate file, build their own
way. So no, also no influence. I don't know enough about InnoDB to say
something for sure, but
Sorry, this came out ugly. I misinterpreted the list filter's
comments, and thought it would post my original message if I replied
to it, but instead it posted my reply including its warning.
Here's my original question, which is indeed about MySQL, although it
does not contain the words "SQL" o
References: <[EMAIL PROTECTED]>
From: Scott Gifford <[EMAIL PROTECTED]>
Date: 09 Apr 2002 15:40:38 -0400
In-Reply-To: [EMAIL PROTECTED]'s message of "Tue, 9 Apr 2002 21:28:35 +0200"
Message-ID: <[EMAIL PROTECTED]>
Lines: 33
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7
MIME-Version: 1.0
Content
