[Martin Lindhe]

peterlaursen wrote on Nov 13 2008, 01:40 PM:

We know it is disputable that we implement DEFAULT as a keyqord. But we need to to enable setting default from context menu of a cell.

But what about NULL, CURRENT_USER and functions/expressions like CONCAT('CURRRENT_USER','_',now()). They are *genuine* MySQL expressions and should *not* be inprepreted as a literal string – not if column is a string type either! Before we implemeted this we were flooded with complaints that NULL, CURRENT_TIMESTAMP, CURRENT_USER etc were quoted as strings!

But use the feature or not as you like!

Okay, I understand the dilemma. Now that you explained to me how to disable it, I am again a happy user!

Again, thank you for your great support

[Martin Lindhe]

peterlaursen wrote on Nov 13 2008, 11:27 AM:

http://webyog.com/faq/content/8/99/en/does…l-keywords.html

1) disable 'smart keywords' in preferences

2) or enclose keywords wiht a special meaning in backticks like `default`

Thank you for your quick response and this grants me a way to work around my issue.

However I would like to argue this is not very “smart” behaviour, since the data type of the field is text.

While forbidding the user to use field names such as “desc” (which you allow btw) and other which would

conflict with the SQL language reserved keywords, this behaviour is (for me at least) most confusing.

Just my 2 cents.

[Martin Lindhe]

Update: The problem no longer appears with wine 0.9.55

Best regards

Martin Lindhe

[Martin Lindhe]

peterlaursen wrote on Jan 30 2008, 03:56 PM:

Please:

1) check tools .. preferences .. editor.

What is the font selected for 'others'. Could you experiment with a few others?

all is the default: Courier New, 9px

peterlaursen wrote on Jan 30 2008, 03:56 PM:

2) could you try install the MS core fonts in Wine.

Please refer to: http://webyog.com/faq/content/31/71/en/can…r-on-linux.html

(download link is there)

the ubuntu package “msttcorefonts” is installed on the system, and courier new is displayed correctly inside sqlyog in the sql query editor & all of these tabs:

1)Result

3) Table data

4) Objects

5) History

only “2) Messages” displays the “chinese”

peterlaursen wrote on Jan 30 2008, 03:56 PM:

3) we would like to know if data in RESULT tab also become chinese if you 'show result in text'

hm, yes. show result in text also displays in “chinese” text

peterlaursen wrote on Jan 30 2008, 03:56 PM:

4) finally:

what is your LOCALE setting?

if non-US could you change the LOCALE in a console and start SQLyog from that console?

Code:

LANG=en_US.UTF-8
GDM_LANG=en_US.UTF-8
LC_TIME=sv_SE.UTF-8

[Martin Lindhe]

peterlaursen wrote on Jan 30 2008, 01:58 PM:

Two more question actually for you!

1)

Is it only *error* messages that display in chinese?

What about *no error* mesages (like '37 rows affected')?

Both error messages & “rows affected” is displayed with “chinese”. however the actual text displays differs.

rows affected: “〨爠睯猨愩晦捥整⥤⠊‰獭琠歡湥਩

绎梀结뜄绑ベ篃箊”

syntax error: 牅潲⁲潃敤㨠ㄠ㘰਴潙⁵慨敶愠牥潲⁲湩礠畯⁲兓⁌祳瑮硡※档捥桴⁥慭畮污琠慨⁴潣牲獥潰摮⁳潴礠畯⁲祍兓⁌敳癲牥瘠牥楳湯映牯琠敨爠杩瑨猠湹慴⁸潴甠敳渠慥⁲✧愠⁴楬敮ㄠ⠊‰獭琠歡湥਩

떉箈뜄绑3컐绎梀结뜄绑3欞绊

peterlaursen wrote on Jan 30 2008, 01:58 PM:

2)

Am I correct in assuming that the MySQL server is 64 bit?

yes. mysql is 64-bit binary, and so is the rest of the system

however, wine is being run through 32-bit compatiblity wrappers (lib32 or something), it works well but i'm not too familiar with how all that works under the hood

this is the default setup for wine on 64-bit systems, and it has something to do with how wine works internally, since it emulates 32-bit versions of windows

[Martin Lindhe]

peterlaursen wrote on Jan 30 2008, 01:28 PM:

Please tell if the Wine and MySQL versions were installed with Linux or if you have updated those from another source!

It is official Wine & MySQL packages from Ubuntu repositories for Ubuntu 7.10 (amd64)

peterlaursen wrote on Jan 30 2008, 01:28 PM:

Please also try to connect and execute ” SHOW VARIABLES LIKE '%character%'; “

.. and paste the result here.

character_set_client utf8

character_set_connection utf8

character_set_database latin1

character_set_filesystem binary

character_set_results utf8

character_set_server latin1

character_set_system utf8

character_sets_dir /usr/share/mysql/charsets/

peterlaursen wrote on Jan 30 2008, 01:28 PM:

I would also like to see your my.cnf file!

it's basically default my.cnf installed by mysql-server ubuntu package. i think the only change i done was the path for error log (/etc/mysql/conf.d/ is empty)

Code:

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# – “/etc/mysql/my.cnf” to set global options,
# – “~/.my.cnf” to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with –help to get a list of available options and with
# –print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain “#” chars…
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0

[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
language = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
# bind-address = 127.0.0.1
bind-address = 0.0.0.0
#
# * Fine Tuning
#
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 128K
thread_cache_size = 8
#max_connections = 100
#table_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
log = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement 🙂
#
# Here you can see queries with especially long duration
log_slow_queries = /var/log/mysql/mysql-slow.log
long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
log_bin = /var/log/mysql/mysql-bin.log
# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * BerkeleyDB
#
# Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
skip-bdb
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI “tinyca”.
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem

[mysqldump]
quick
quote-names
max_allowed_packet = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer = 16M

#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the NDB Data Nodes (ndbd processes)
# not from the NDB Management Nodes (ndb_mgmd processes).
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1

#
# * IMPORTANT: Additional settings that can override those from this file!
#
!includedir /etc/mysql/conf.d/

peterlaursen wrote on Jan 30 2008, 01:28 PM:

Please confirn too that you were connected to the same server with all those clients? This is important!

all of this is from my mysql setup on localhost (yes it gives these chinese errors 😉

peterlaursen wrote on Jan 30 2008, 01:28 PM:

This is very weird to me how this can happen. With UTF8 such charset 'mess-ups' should be prevented by the encoding itself – it has no 'endianness' and the byte patterns that could mess up like this *should* be impossible! With UCS2 'mismatching' with multibyte non-unicode encodings (such as 'Big5') is theoretically possible!

Maybe it isnt worth your effort to look too much into this. the bug might just as well be inside Wine somewhere.

Perhaps some win32 widechar-stringhandling function in either libmysql (do you link statically with libmysql.lib or use other mysql-client?) or sqlyog.exe works incorrect in current wine version? (just speculating)

if an newer version of Wine resolves this issue I'll post here to let you know.

[Martin Lindhe]

peterlaursen wrote on Jan 30 2008, 10:29 AM:

My mistake then. I must have confused something. But it took very long time to retrieve that picture last night.

Anyway .. did you try an erroneous message with another client like command-line?

Yes, i tried both with command line client & “MySQL Query Browser”. error messages show up correctly

[Martin Lindhe]

peterlaursen wrote on Jan 29 2008, 11:25 PM:

2)

Please read:

http://dev.mysql.com/doc/refman/5.0/en/comp-err.html

You are sure that the error message file used in that system is not chinese?

It does not do with other clients? Please try an erroneous query from command line client (just “SELECT blahblah”!).

Execute on a Linux shell (do not connect from a Windows machine). Alternatively try MySQL Query Browser ..

Locale on my machine is set to swedish. I get same “chinese” error messages both when connecting to mysql server on localhost, and on

a mysql server on remote host running different linux distro, with en_US locale.

By connection from command line mysql client, error messages appear as normal.

peterlaursen wrote on Jan 29 2008, 11:25 PM:

3)

What is wrong about Chinese? It is a very informative language! 🙂 Jokes apart .. we have no such reports before!

I think this must be a configuration issue on your system or a silly mistake with the MySQL build distributed with that distro!

Hehe 😉 If you looked at the image its just some chinese (or japanese?) letters together with other random letters. It looks like mis-interpreted/corrupted unicode text or something to me.

It might very well be some issue with Wine, because I think at one time these error messages did show up correctly in a slightly older version of Wine. But I didn't really start to pay attention until the strange chinese text started appearing 🙁

[Martin Lindhe]

peterlaursen wrote on Jan 29 2008, 11:29 PM:

I do not know what happened, but know I can see the image. Probably it was because it was a little big and took some time to transfer!

With a reasonable image format , 'cut', and compression you could have saved our server 20MB of diskspace. It is rather easy to tell the same message with around 100KB! Please observe!

Well i placed the image on my own web server startwars.org and just linked it in the post with the [img]tag, so i didnt “waste” more than 100 or so bytes my orginal post took on your server. Also, the image is about 260kb large, not 20MB… ?

[Martin Lindhe]

peterlaursen wrote on Nov 19 2007, 11:19 AM:

Thanks for your feedback!

can you tell if you use COMMUNITY or ENTERPRISE version?

I'm using the community version currently. Sorry for not specifying that in the original bug report.

[Martin Lindhe]

peterlaursen wrote on Nov 16 2007, 04:51 PM:

Please verify the fix with 6.14 RC.

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

Yes! Both the issues i described in the first post appears to have been fixed!

Thank you so much!

Now sqlyog under wine appears to work identical to the windows version, but i am not using every features of sqlyog so maybe there is some issues still. Great news for linux users 🙂

[Martin Lindhe]

Mahesh wrote on Nov 16 2007, 08:49 AM:

Issue Confirmed ! (crash)

We will fix this with high priority..

Thanks for reporting

thank you very much!

[Author]

Posts