[peterlaursen]

Thanks for the details! We will study this!

Still it might help if you created a small 'dummy' table with a few rows of data, exported it, zipped and attached here.

What is the locale/language of you windows?.

Please explain 'it depends on the substring length'.

In SQLyog “SELECT 'ö'” and “SELECT substr('ö',1,200)” should return the same. 'ö' simply. I cannot make it do different than that. See attached!

[peterlaursen]

we have discussed that idea before.  I think first time about 2 years ago!!

It is not plain easy!  because when data are stored in a BLOB filed there is no file and no file extension, so there is no information about what program to use.  You are welcome to detail …

We have several issues with the BLOB viewer and with binary data in general (BIT type, VARBINARY).  We have given priority to other issues till now.  I hope that we can pay attention to this during the summer.

[peterlaursen]

aha ..

when SJA is started from within a PHP script it runs with the privileges of Apache.  Did I get it right?

Did you install Apache and SQLyog as different users?

[peterlaursen]

we need more info!

1) Can you tell if this happens with the first row of data or later?  this is important because it will give a hint if this is dataspecific or not.

2) SQLyog version and MySQL version.  

3) can you attach the jobfile, please.  A dump with a few rows on each host to reprouce with would be nice too!

[peterlaursen]

It is reproduced now.

It is a bug in early MySQL 4.1.x that was fixed in more rounds but only fixed ultimately in 4.1.12!  You can see details in the server changelogs.

We also know a workaround for this, but we do not like it, because it is very dirty and unhealthy SQL we will need to send!  We also need to be perfectly sure that that are no unwanted side-effedcts (for ALL locales and non-western users is the problem!).

We will need a few days for considering this, but anyway next 6.0 release will be in about 1 week only, so we have the time to think about it!

It is working with MySQL 4.1.10 (as shipped with RHEL4 and Fedora3).

[peterlaursen]

we installed a 4.1.7 mySQL server on Windows.  the issue that you report is not reproducable.

Please explain very much in detail as I requested before!

[peterlaursen]

please also explain “I cannot execute any queries to a server running mysqld 4.1.7” — it it only queries that you write yourself in the SQL pane?  What about the queries that are generated by SQLyog?

Please explain in details what happens from the very moment you (try to) connect .. what you are doing and what response you get on everything?

[peterlaursen]

the one thing I do not fully understand is how it happens that NOTHING is written to HISTORY.  There must be at least one statement sent if the server returns an error.  Not even 'show variables …' or 'set names —' in history?

Is there a 'general log' on this server?

However upgrading RPM-based MySQL is very simple actually and I would recommend.  It was given the predicate 'stable' when released, but check yourself the changelogs for bugfixes between 4.1.7 and 4.1.22!

Please confirm this:  this error message appears at the very moment you connect with SQLyog 6 beta? Do you have an option to use other connection methods?-

I do no say that this is proven to be a bug with MySQL. But if it is, we may be able to do some 'workaround'. But with that old server version there are limits to how much effort we will spend on that!

is it possible to get temporary access to the server?

Did you try from different client machines?

[peterlaursen]

Holy Cow … Ri Coder is back   😉

One thing I think you should change is this “SQLyog works on the Windows platform starting from Windows 95 to Windows Vista”.

We have not tested on W95 for very long time.  Nobody knows if it works anymore!

Also Unicode version currently supports from 2K upwards and Unicode with any Windows version before W98SE is not possible 

(And I frankly do not know how long it is worth going on supporting W98SE actually. I think we should if it is easy, but it is not worth having a lot of trouble with – we can maintain the 5.x tree with critical fixes for 98SE users for a while!).

Wait for Rohit to get back from US, and I think we should make the final decision in this respect!

[peterlaursen]

I now notice this

Quote:

a server running mysqld 4.1.7

4.1.7 was the first version in the 4.1.x tree that had the 'stable' predicate.  But the charset concept and unicode implementations were new.  And still very buggy.

I will have to say that we cannot support server versions antique as this one!

What OS is this server running?  There is a lot of red hat's running 4.1.10 in the world (the one that it shipped with originally).  But 4.1.7 is a rare version! (and the before mentioned red hat's should have 4.1.20 installed.  Official RH RPMs are available at least for 4.1.20.  We did this on this server itself about 9 months ago and that solved several issues!

[peterlaursen]

If this:

http://webyog.com/faq/33_128_en.html

was the question you also find the answer there!

You can of course install any old version again if you have the installer and the registration code.

But please explain why did it 'stop working' and what does it mean to 'manage' the upgrade.  technically/financially?  do you have any issue with our Customer Portal?

[peterlaursen]

please tell the exact server version!

also if you can connect with commandline please check if it does better!

I am not sure, but this looks mostly like a server issue (a bug with the implementation of the SUBSTR() function). I will not make much sense to try reproducing with another server version! I cannot reproduce here with MySQL 5.0.37 and Danish characters

[peterlaursen]

It does not genereate a complete script for the sync job.

It compares a  large number of rows on both hosts using checksum algoritms.  If there is a difference between the two, the beforementioned routine is executed recursively and the individual rows that need to be INSERTed, DELETEd or UPDATED are located.  Next the operations are performed on the rows where it is required, and everything starts over with the next rows until the end of that table has been reached.

Did that answer your question?

[peterlaursen]

BTW: you will not need Access installed to use the ODBC driver.

I wonder if Office 2007 replaces the driver when it installs?

If ther is a NorthWind database shipped with this Office 2007 trial, then please try this one as well.

I am no sure taht we can find a Northwind database older than 2002 or 2003.

We will try various combinations now.

I remember very clearly that I imported/migrated the NW database from a Office 2003 system with SQLyog 6.0 beta1 – also on XP SP2.

[peterlaursen]

We are working on the crash thing.

About the Migration trouble. Two questios:

1) Did you unhide the hidden system tables in the Access database. To import Foreign keys you must.

2) Did you select 'abort on error' or not?

[Author]

Posts