[peterlaursen]

User name cannot be name of database! It must be a user with that database

When doing a DATA sync you have two independent MySQL logon's at the same time 

[peterlaursen]

Quote:

SQLyog doesn't complain

No if the server does not, SQLyog does not either.  

The server 'silently' does what it does.  

It does not even produce a warning (try “show warnings;” yourself).  

There is no way for SQLyog to tell that the server changed the SQL 'silently' when executing it.

[peterlaursen]

I think you mistake the two programs:

SQLyog.  This is a Windows program and a GUI program too. To run it on Linux you will need to run it in WINE.  Please refer to

* http://webyog.com/faq/31_71_en.html

I do not know if CentOS is distributed with Wine (I do not think so), but you can start the search for Wine at

* http://www.winehq.com

SQLyog Job Agent (SJA): This is a command line program.  On Linux it will not need to be installed.  To execute it just navigate to the folder where it was unpacked and enter “./SJA {parameterlist}” from a command shell.  For 'parameterlist' see:

* http://webyog.com/faq/27_114_en.html

and this FAQ category could be useful in general:

* http://webyog.com/faq/category0.html

[peterlaursen]

Quote:

This is what I have for the DB path: C:August 9 Testvbulletin.sql

You should not use a FILE PATH to the database.  To access a MySQL database you will need to use a client and enter

* host

* user

* password

* port

.. basically!  

But I am not sure I understand. Could you possibly post some screenshots of what works and what does not? You can fake details. You can also create a ticket?

[peterlaursen]

The same details should work.  If you saved the connection details in the Connection Mananger just choose from the dropdown.

[peterlaursen]

not quite.

http://dev.mysql.com/doc/refman/5.0/en/sto…quirements.html says

“Prior to MySQL 5.0.3: L + 1 bytes, where L <= M and 0 <= M <= 255. MySQL 5.0.3 and later: L + 1 bytes, where L <= M and 0 <= M <= 255 or L + 2 bytes, where L <= M and 256 <= M <= 65535 (see note below)." note 1) the limitation is in bytes not in characters. So it depends on the character set …

2) “<= 65535" refers to the storage. Some of those bytes are needed for internal adressing inside the tablespace.

Here I can create a varchar(65500) with a latin 1 table. Won't that do for you?

[peterlaursen]

On MyISAM a KEY can only be 1000 bytes.  Do you use a BLOB/TEXT field for a key?  I think so!  Then you must specify a KEY lenght of max. 1000 before you can change table type.

Do so from table context menu .. manage indexes .. edit the index

[peterlaursen]

You can then post in your own thread in the MySQL Forums that you found the solution after asking here!

[peterlaursen]

With SQLyog ENTERPRISE you have the DATA SYNC tool.

this article explains:

http://webyog.com/en/whitepapers/Using_SQL…L_Databases.pdf

please read and try to understand.

[peterlaursen]

We have not been able to reproduce a CPU load as high as you report.

But there is a change between 5.22 and 5.23 in 'CPU load behaviour'.

We will search for that!

[peterlaursen]

This is reproduced (and partially explained) now.

The problem is that when you click a database in second connection a USE statement is sent.

If you swith back to first connection by clicking the title bar of the connection window (and doing nothing else before trying to kill the connection) no new USE statement is sent. The USE statement from second connection is still the active one.

But USE statements should be specific for each connection, I think.

And personally I am not sure why we need to address some specific database here at all!

We will study our own code again! 

[peterlaursen]

Please tell how you connect!

I briefly tried to reproduce this but I cannot.  

We will now try more systematically!

[peterlaursen]

Only the 5.23 betas are affected.  Not 5.22.

Such detail will be fixed in next release of course!

[peterlaursen]

Thanks for your report.

We will research into that now!

[peterlaursen]

Thank you!

yup.  And 53 is a very special age as 53 is a Prime Number.  There is nothing like it! <_<

[Author]

Posts