On 16-11- 2005, at 13:35, Radek Svarz wrote:
not sure if that helps you. We had to rollback and use 4.0.x (with
win-1250 and iso-8859-2) because the support of UTF-8 and collation
in 4.1 for the czech lang. was not properly done.
Well I found sollution, cludge but it works. I will create
not sure if that helps you. We had to rollback and use 4.0.x (with
win-1250 and iso-8859-2) because the support of UTF-8 and collation in
4.1 for the czech lang. was not properly done.
I'll give 4.1 another try tomorrow and let you know.
sorry, no help today.
Radek
On 11/16/05, Nebojša Đorđević
On 16-11-2005, at 13:12, Radek Svarz wrote:
There are diffs between 4.0.x 4.1.x and 5.
My local version is MySQL 4.0.23_Debian-3ubuntu2.1-log and TextDrive
is using MySQL 4.1.14-log, and probably that is a problem. Any
solutions?
---
Nebojša Đorđević - nesh
Studio Quattro - Niš - SCG
h
What's the MySQL version?
There are diffs between 4.0.x 4.1.x and 5.
RadekOn 11/16/05, Nebojša Đorđević - nesh <[EMAIL PROTECTED]> wrote:
I'm hitting interesting problem with MySQL hosted on TextDrive. Allcharacter encoding is set to utf-8 but I'm still getting a '?' forall accented characters fr
I'm hitting interesting problem with MySQL hosted on TextDrive. All
character encoding is set to utf-8 but I'm still getting a '?' for
all accented characters from all queries.
They recommended that 'SET CHARACTER SET utf8' should be sent after
opening connection to counter this to force
