Can't copy tables — 'Default charset=latin1'

[walkman]

I get a 1064 error when I try to copy tables from local to server.

It turns out that my local instance is 4.1.9 & my server instance that I'm copying to is 4.0.18

Is there a way around this error?

Thanks.

[walkman]

Ok, it's a bit of a hassle but I was able to solve the problem by doing the following:

1) export the table as a batch script from the source database

2) switch to the target database

3) open the batch script

4) Edit out the “default charset=latin1” reference in the SQL create statement

5) Run the script

Obviously, this isn't effective for an on-going syncronization, but it works on an occasional basis.

Please let me know if there is a better “fix”.

[peterlaursen]

You found the solution yourself! Thats what I do too! And I know no better fix at the moment.

The “fix” that I do to be able to use SJA is to have more versions of the MySQL server installed (actually I have three). I don't run them simutaneously but edit the server variables, stop and restart the server with “MySQL Administrator”. Actually I believe that 4.0.x and 4.1.x can use the same datadir (4.x and 5.x can't). Actually I use the same datadir with 4.0 and 4.1 and I believe it is in 4.1-format. But don't edit users with the “wrong” MySQL version and be careful with the use of timestamps!

I posted some screenshots of the procedure that I follow here

http://www.webyog.com/forums/index.php?act…=ST&f=10&t=1427

[Shadow]

And do not use InnoDB because its engine has been changed in 4.1.1 by adding multiple namspace support!

[Fox]

Try the “-compatible=mysql40” option.

[Ritesh]

Shadow wrote on May 25 2005, 08:58 AM:

And do not use InnoDB because its engine has been changed in 4.1.1 by adding multiple namspace support!

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

Nice to have you back Shadow 🙂

[Ritesh]

walkman wrote on May 24 2005, 04:18 PM:

I get a 1064 error when I try to copy tables from local to server.

It turns out that my local instance is 4.1.9 & my server instance that I'm copying to is 4.0.18

Is there a way around this error?

Thanks.

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

This issue has already been fixed in 4.2 BETA 6 development tree. Now SQLyog will check the source and target MySQL server and if required will construct the CREATE TABLE statement itself. It will not use the CREATE TABLE statement returned by:

Code:

show create table tablename

PS: SQLyog will still use SHOW CREATE TABLE SQL in Export As SQL Statements option as we dont know the TARGET MySQL server version.

[peterlaursen]

@Ritesh

That post of Shadow was an old one … 2005-05-25 😛

It is Fox that revives an old thread!

[Ritesh]

Bah, I didnt see the date 😀

[Author]

Posts