[motin]

motin wrote on Jan 17 2006, 03:27 PM:

I'll return to this post with success-status…

[post=”8492″]<{POST_SNAPBACK}>[/post]

No success. Upgrading to 4.1.16 did not solve the problem.

I found another way to rename the case though: renaming the files from MySQL-data directory. This will make the file-names correct. I am not sure how this affects indexes etc, but this seems to be me best bet as every ALTER or CREATE command converts everything to lowercase…

I want to verify that my lower_case_table_names-setting has kicked in, do you know a way to do this at runtime? (Google isn't much helpful this time… Nor is the MySQL-documentation search)

[motin]

peterlaursen wrote on Jan 17 2006, 12:18 AM:

Looks very much like this one:

http://www.webyog.com/faq/26_25_en.html

Yes indeed it does, although all my tables

are MyISAM, not InnoDB.

peterlaursen wrote on Jan 17 2006, 12:18 AM:

… and use the server directive lower_case_table_names=2 in the [mysqld] section of the my.ini -file.

So I have. Thanks for clarifying.

peterlaursen wrote on Jan 17 2006, 12:18 AM:

It should solve the issue to upgrade to MySQL 4.1.13 or higher.

Despite having MyISAM-tables this seems to be my best bet. Thanks!

I'll return to this post with success-status…

[motin]

Ritesh wrote on Oct 18 2005, 06:03 PM:

You can use Tables -> Reorder Columns to reorder the columns using SQLyog GUI.

[post=”7625″]<{POST_SNAPBACK}>[/post]

Great!

I feature request then would then be a minor change in the UI, that informs the user of this when viewing the Alter table-dialogue

Ritesh wrote on Oct 18 2005, 06:03 PM:

Sturcture sync does not support reordering columns. This feature is already in the TO-DO list of SQLyog.

Is the to-do list publicly available somewhere? I searched for it in the faq, but could only find: http://webyog.com/faq/index.php?action=art…&highlight=todo

It mentions: “Further there is a TODO list of ideas and user requests that will be implemented when the code module involved is recoded next time.”

But does not provide a link to this.

[motin]

For help fixing this, this is how to alter field-orders:

To reorder the columns of your table, you can use the ALTER TABLE syntax, since as of MySQL 4.0.1, the keywords FIRST and AFTER can be used in a CHANGE or MODIFY command.

Example:

mysql> describe example_table;

Code:

+————-+————+——+—–+———+—————-+
| Field       | Type       | Null | Key | Default | Extra          |
+————-+————+——+—–+———+—————-+
| id          | int(11)    |      | PRI | NULL    | auto_increment |
| columnA     | bigint(20) |      |     | 0       |                |
| columnB     | text       |      |     | 0       |                |
+————-+————+——+—–+———+—————-+

3 rows in set (0.00 sec)

mysql> ALTER TABLE example_table CHANGE COLUMN columnB columnB TEXT NOT NULL AFTER id;

Query OK, 3 rows affected (0.01 sec)

Records: 3 Duplicates: 0 Warnings: 0

mysql> describe example_table;

Code:

+————-+————+——+—–+———+—————-+
| Field       | Type       | Null | Key | Default | Extra          |
+————-+————+——+—–+———+—————-+
| id          | int(11)    |      | PRI | NULL    | auto_increment |
| columnB     | text       |      |     | 0       |                |
| columnA     | bigint(20) |      |     | 0       |                |
+————-+————+——+—–+———+—————-+

[motin]

I always do a search in forums before posting, but still I managed to doule-post. Searching for “large tables” gave me a post that addresses the same issue.

Highlights:

Quote:

My theory is that if I can get them copied the once then synch should be ok as there are minimal differences to deal with.

&&

Quote:

For a big table, it is recommended that you import the data in the target server for the first time and then sync it.

Now I know what to do: Import the data through standard methods instead of the Synchronization Wizard. Then use the wizard for what it is made for: synchronization!

[Author]

Posts