Hi all I've been started to look at Drizzle compability with MySQL, and the first issue i got is the Charset and Collation
I've been looking through Drizzle documentation and it said that currently Drizzle only support utf8 charset and collation. But as i seen the code on latest trunk, phpMyAdmin simply disable it rather than set it to utf8.
As i tested on Drizzle7 2011.03.13, we can look at supported charset by query: SELECT * from DATA_DICTIONARY.CHARACTER_SETS; As replacement of SHOW CHARACTER SET; on MySQL
And for the collation: SELECT * from DATA_DICTIONARY.COLLATIONS; As replacement of SHOW COLLATION; on MySQL
But, the table structure is little bit confusing here, because in MySQL we can match the `Charset` field on both result, but in Drizzle i've to match `CHARACTER_SET_NAME` on charset result and `DESCRIPTION` on collation result.
At least, now phpMyAdmin can show correct charset and collation on the Charsets menu. I already send patch for this issue [1]
But, i got another issue, for example when submit Create table form, it thrown error "CHARACTER SET" because it's removed on Drizzle [1], but "COLLATE" seems to be supported [2]
I'll give more investigation on this issue.
[1] https://sourceforge.net/tracker/?func=detail&aid=3280876&group_id=23... [2] http://docs.drizzle.org/mysql_differences.html#objects-removed [3] http://docs.drizzle.org/create_table.html?highlight=create%20table#data-type
Regards Azhari Harahap http://azhari.harahap.us
Hi
Dne Fri, 8 Apr 2011 19:53:27 +0700 Azhari Harahap azhari@harahap.us napsal(a):
I've been started to look at Drizzle compability with MySQL, and the first issue i got is the Charset and Collation
I've been looking through Drizzle documentation and it said that currently Drizzle only support utf8 charset and collation. But as i seen the code on latest trunk, phpMyAdmin simply disable it rather than set it to utf8.
As i tested on Drizzle7 2011.03.13, we can look at supported charset by query: SELECT * from DATA_DICTIONARY.CHARACTER_SETS; As replacement of SHOW CHARACTER SET; on MySQL
But it should report only utf-8 right?
And for the collation: SELECT * from DATA_DICTIONARY.COLLATIONS; As replacement of SHOW COLLATION; on MySQL
This should be already used in master.
But, the table structure is little bit confusing here, because in MySQL we can match the `Charset` field on both result, but in Drizzle i've to match `CHARACTER_SET_NAME` on charset result and `DESCRIPTION` on collation result.
At least, now phpMyAdmin can show correct charset and collation on the Charsets menu. I already send patch for this issue [1]
You seem to be late, Piotr sent patch earlier and is was already merged.
But, i got another issue, for example when submit Create table form, it thrown error "CHARACTER SET" because it's removed on Drizzle [1], but "COLLATE" seems to be supported [2]
Yes, there are definitely more such differences, that's why there is GSoC project for this :-). If it would take just few hours to fix, it would be already done.
Hi
On Apr 11, 2011, at 7:54 PM, Michal Čihař wrote:
As i tested on Drizzle7 2011.03.13, we can look at supported charset by query: SELECT * from DATA_DICTIONARY.CHARACTER_SETS; As replacement of SHOW CHARACTER SET; on MySQL
But it should report only utf-8 right?
Yes, currently only utf8 supported, but this value may/sure be increased on the future.
And for the collation: SELECT * from DATA_DICTIONARY.COLLATIONS; As replacement of SHOW COLLATION; on MySQL
This should be already used in master.
Yes, i've just check it out :)
At least, now phpMyAdmin can show correct charset and collation on the Charsets menu. I already send patch for this issue [1]
You seem to be late, Piotr sent patch earlier and is was already merged.
Yes, kinda late, i just realize it after create the patch report on the tracker, but i already close it and mark as duplicate.
But, i got another issue, for example when submit Create table form, it thrown error "CHARACTER SET" because it's removed on Drizzle [1], but "COLLATE" seems to be supported [2]
Yes, there are definitely more such differences, that's why there is GSoC project for this :-). If it would take just few hours to fix, it would be already done.
Thanks for the hint :)
Btw, i've send another patches to list table structure on Drizzle by change the "SHOW FULL FIELDS" to "SHOW COLUMNS" [0], there is some limitation because some value is missing, like collation and key, but at least now PMA can list table structure correctly.
[0] https://sourceforge.net/tracker/?func=detail&aid=3283624&group_id=23...
Regards Azhari Harahap http://azhari.harahap.us
Hi
Dne Wed, 13 Apr 2011 18:08:01 +0700 Azhari Harahap azhari@harahap.us napsal(a):
On Apr 11, 2011, at 7:54 PM, Michal Čihař wrote:
As i tested on Drizzle7 2011.03.13, we can look at supported charset by query: SELECT * from DATA_DICTIONARY.CHARACTER_SETS; As replacement of SHOW CHARACTER SET; on MySQL
But it should report only utf-8 right?
Yes, currently only utf8 supported, but this value may/sure be increased on the future.
Well as one of features they did mention from beginning is remove all handling for charsets, I really doubt this will be the case.
-
Azhari Harahap -
Michal Čihař