[peterlaursen]

The “copy database to other host” only shows databases that are 'open'.

So first you must open a connection to the server where the target database is/should be. And if you don't want to add data to an existing database here you must start creating an empty database.

[peterlaursen]

and here:

http://www.webyog.com/faq/28_72_en.html

[peterlaursen]

You can use SQLyog Enteprise including the SJA for Windows with WINE:

http://www.webyog.com/faq/5_71_en.html

attached picture shows sja for windows running under wine WITH SSH TUNNELLING to the remote host

So you won't have to buy a Windows machine or a Windows OS.

Just buy SQLyog Enterprise! 😀

[peterlaursen]

hmmmm …

I understand you like this:

You have a webhost with limited space and a localhohost with more space. Data added at the webhost should be transferred to the local host.

If that is it you can run a one-way sync webhost >> localhost an use the NEVER DELETE option.

Was that it? If not you must explain somewhat better!

[peterlaursen]

is it this one: http://epf.molhanec.net/

If not what then ??

SQLyog does not use PHP – it connects directly to the database. The SJA (SQLyog Job Agent) however can be executed from within a php script.

You must explain more in detail what your are trying to do!!

But please also read the program help file and the FAQ

http://www.webyog.com/faq/

http://www.webyog.com/faq/16_4_en.html

If you intend to use HTTP-tunneling you also only need the PHP-tunnelling script that is included with SQLyog

http://www.webyog.com/faq/category21.html

[peterlaursen]

Just a follow up!

I have now been running SQLyog almost exclusively on wine for the last about 4 days. It performs better here than it does on Win XP (Win and *nix is a dualboot on the same machine with hardware: Athlon XP+1770, 1 G DDR 2100 RAM). Or maybe it is MySQL that performs better on Linux? And I have not had one single 'hang' or 'crash' with neither 4.2 beta5 nor RC1.

[peterlaursen]

@shoyu

Or you could write Nombre d'années – as you would do in handwritten SQL according to the general rules of using escape characters within strings. But yes I think that I remember that you can escape ' with one more ' too. 🙂

But we agree SQLyog should handle escaping automatically here as anywhere else …

The point/explanation is that SQLyog encloses all string with the ' character when building SQL, so

Code:

Nombre d'années

becomes

Code:

'Nombre d'années'

becomes in the ALTER TABLE staement after being 'processed by SQLyog. Thus the string is only

Code:

Nombre d

and

Code:

années'

is garbage! And MySQL raises an error.

[peterlaursen]

I agree!

All personal settings and files should be availabale for the next install, if there will ever be one.

[peterlaursen]

Personally I don't think the personal folder should have much attention. Instead a 'favourites' system should be implemented that links to txt/sql filles saved anywhere on the system.

Couldn't replace your one dot with some other character?

[peterlaursen]

did you tru 4.2 RC1 ??

It is somewhat difficult for me to test when I don't have your keyboard but the danish characters – æøåÆØÅ – become mapped to cyrillic characters when I set cyrillic font.

Get it from the beta5 link 😆

[peterlaursen]

Nope!

But maybe you should learn about the 'Binary Log'? It is just like a tape recorder recording everything that happens to your database.

If you had this one active with your database you could restore your latest backup and 'replay' the binary log from the point of time of the backup to the point of time where something went wrong.

It is all in the MySQL documentation. They also published an article on it some 4-6 months ago. Must be in their archives.

[peterlaursen]

@ ritesh

you write

Quote:

SJA for Windows is case insensitive but SJA for Linux is case sensitive and thus the difference.

Well yes I can see that! Obviousjt! But should it be like that you think? I think that all programs and OS-versions should be able to run in 'case-sensitive' or 'case-insensitive' mode. Simply because it is the 'case mode' of the server(s) that should decide. To me it is obvious that this is a rule a client must obey.

The triggy things happen when you are working with two connections of two different OS's that have different 'case-mode' – not to speak of the situation (that admittedly is mostly hypothetical!) where two or more DB's or tables on *nix are identical in 'case-insensitive' mode – like ´text´and ´TEXT´. Further there is a tricky thing with Mac-OS: it is 'case-sensitive' or 'case-insensitive' dependent on which filesystem the system runs on.

In these cases the user must decide – a pop-up or a setting.

[peterlaursen]

I am sorry .. now I understand!

You are right. Ritesh may be able to give a better explanation, but a complete 'overhaul' of all charset issues is planned for version 4.3.

[peterlaursen]

@Ritesh

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

It is Fox that revives an old thread!

[peterlaursen]

And the fonts display problem i solved. 😀

Just install these fonts:

http://www.zeuscat.com/andrew/software/corefonts/

in WINE

shell> path/fontname.exe

and repeat for each font.

[Author]

Posts