[peterlaursen]

your dump is not so easy to use as there are no 'create table' statement.

But basically please try 6.02/6.03 beta .. we do not support 5.19 any more and never claimed it was fully unicode compliat!  6.x is!

[peterlaursen]

no!

why don't you have a primary key in your tables, so that you wont get any dublicates?

[peterlaursen]

Basically I think that SQLyog inserts correctly and PHP does not!

SQLyog shows data as they are stored in the database!

refer to those two discussions:

http://www.webyog.com/forums//index.php?showtopic=3284

http://www.webyog.com/forums//index.php?showtopic=3204

1)

Please dump a small table with SQLyog 'export', zip and attach here!

Once opened in NOTEPAD it will be easy to see if data are really stored in the database as utf8!

2)

Please also answer:

MySQL version?

SQLyog version?

[peterlaursen]

OK .. thanks for the reply!

Please also tell the Wine version.

“wine –version' in a command shell will return the version!

but I do not think it is that.

Could you try creating a database with utf8?  In SQL ” CREATE DATABASE CHARSET UTF8 “.

Next try to repeat with this database!

1:

| character_set_system | utf8 |

and

2: Illegal Mix of collations (latin1_swedish_ci,IMPLICIT ) and (utf8_general_ci_CORECIBLE) for operation

clearly tells that it uses the “character_set_system” for the data in the grid.

We will have to analyze this a little more!

[peterlaursen]

Please tell: how do you imagine the output of such 'data comparer' ?

SQL INSERT/UPDATE/ DELETE statements?

Some kind of table view ?

[peterlaursen]

We will release the next SJA for Linux (version 6.0x) very soon.  Probably on Friday.

Actually I am not sure if 5.0 will work (and I have no option to test right now!).  But I think it will if charset settings in server configuration is the same and if you use the same tag for both connections.

Version 6.0 will definitely work with data stored on the server with ALL charsets, including unicode (utf8, ucs2).

[peterlaursen]

😮  I think Rohit has a point ….

[peterlaursen]

There is no info we can use!

SQLyog Program version?

MySQL version you are importing to?

What kind of ODBC-source?

What kind of DSN ('file','user' or 'system') ?

Also please try SQLyog version 6.03 beta1 if you did not already!

[peterlaursen]

let me add that MONyog will never work in Win98. Monyog installs as a service – Win98 has no 'services' !

[peterlaursen]

well it normally works with varchars!

Please execute ” SHOW variables like '%character%' ” and paste the results!

Are you running on Windows or Wine/Linux?

there are such issues with mysql, including this one:

http://bugs.mysql.com/bug.php?id=26905

.. but if this is a mysql bug too we would like to report it explicitly.  Please assist in this!

[peterlaursen]

I also think that you study the program help file a little.

Especially the last example in the paragraph on the Query Builder.

With this type of grid we cannot support “A AND (B or C)” directly, it will need to be rewritten (using common boolean mathematics)

– like “A AND (B or C) = ( A AND B ) OR ( A AND C )“

Have a look on how you treat a condition that year(delievery) shall be AND'ed with country like 'India' OR 'Pakistan' etc in that last example of the program help file.

[peterlaursen]

what is it you call 'accentuation' ?  like this: ” á ”  ?

we just dicovered another issue with the 'portuguese tilde accented a' ( ã ) in column names and when updating from the RESULT tab.

So we will check for more such issues now!

[peterlaursen]

What you get depends on how you enter in the grid!  So if you posted a screenshot of your grid I would be able to tell if this is a bug or not!  You can generate both!

the two rules are:

1) what is entered in the same row of the grid is logically AND'ed and the rows are logically OR'ed

2) criteria going to the WHERE and HAVING clause are treated independently

[peterlaursen]

We believe that we fixed this now.  We will release version 6.03 shortly with the fix.

[peterlaursen]

We believe we fixed that now. We will release 6.03 beta 1 shortly with the fix!

[Author]

Posts