When I change the encoding from the default in MySQL 4.1 to let's say cp1251, I have to run a query "SET names cp1251" to see the data properly in web pages. In SQLyog however this does not work and all encoded data is retured as question marks.
phpMyAdmin properly shows all the data...
Will automatic encoding support be implemented? or is there a way to set the encoding for a certain connection?
Full Version: 4.1 Encoding Problems
see Shdows' comment at the end.
http://www.webyog.com/forums/index.php?showtopic=1402
did that do the trick.
"encoding" is not a word in MySQL terminology. It's purely a browser terminology.
http://www.webyog.com/forums/index.php?showtopic=1402
did that do the trick.
"encoding" is not a word in MySQL terminology. It's purely a browser terminology.
From MySQL doc's
http://dev.mysql.com/doc/mysql/en/charset-connection.html
http://dev.mysql.com/doc/mysql/en/charset-connection.html
When I start a new connection to MySQL 5.1 with SQLyog 4.2 beta2, RESULT tab shows:
show variables like '%character%'
Set character_set_connection=latin1
Set character_set_results=latin1
Set character_set_client=latin1
*****************************************************
@ritesh: some questions
1) I guess these values are the default server settings?
(fetch by the 'show variables' statement.
2) shouldn't it do this too:
SET collation_connection = @@collation_database
3) what pvutrix request is actual a tab more in connections manager with that sorts of settings. In case user has specified these parameters, they shall be used and "show variables like '%character%'" shall not be sent. Actually in an international environment I think it is quite important to be able to operate smoothly in more 'locales'. Comment ?
show variables like '%character%'
Set character_set_connection=latin1
Set character_set_results=latin1
Set character_set_client=latin1
*****************************************************
@ritesh: some questions
1) I guess these values are the default server settings?
(fetch by the 'show variables' statement.
2) shouldn't it do this too:
SET collation_connection = @@collation_database
3) what pvutrix request is actual a tab more in connections manager with that sorts of settings. In case user has specified these parameters, they shall be used and "show variables like '%character%'" shall not be sent. Actually in an international environment I think it is quite important to be able to operate smoothly in more 'locales'. Comment ?
YES !!
I propose that 4.3 will have a TAB more in connections manager named "locale settings", with three possible choices.
1) use server default
2) use database default (will query locale settings from first database specified in "server" TAB
3) manual settings
It would be appropriate to introduce that with 4.3 (with Unicode support).
Maybe there are other connection-specific settings than local's that are relevant ?
check from http://dev.mysql.com/doc/mysql/en/server-sql-mode.html .
Those "modes" can from MySQL 4.1 be operated independently by each connection/client
I propose that 4.3 will have a TAB more in connections manager named "locale settings", with three possible choices.
1) use server default
2) use database default (will query locale settings from first database specified in "server" TAB
3) manual settings
It would be appropriate to introduce that with 4.3 (with Unicode support).
Maybe there are other connection-specific settings than local's that are relevant ?
check from http://dev.mysql.com/doc/mysql/en/server-sql-mode.html .
Those "modes" can from MySQL 4.1 be operated independently by each connection/client
As you know, we plan to completely overhaul the language issues in v4.3. This proposal is already in the plan for v4.3 where a user can actually specify the collation to be used.
With v4.3, issues similar to PvUtrix's will be fixed
With v4.3, issues similar to PvUtrix's will be fixed
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.