Re: MySQL and Unicode

2004-04-20 Thread Stormblade
On Tue, 20 Apr 2004 11:49:46 -0500, Paul DuBois wrote: >>> Make sure the server really is picking up the option value: >>> >>> >>> SHOW VARIABLES LIKE 'character%'; >>> >>> >>> Look for 'character_set_server'. >>> >>> >>> If it's utf8, then perhaps your GUI tools are overriding the >>> setting? Dun

Re: MySQL and Unicode

2004-04-20 Thread Stormblade
On Tue, 20 Apr 2004 12:13:07 -0500, Paul DuBois wrote: > At 13:03 -0400 4/20/04, Stormblade wrote: >> On Tue, 20 Apr 2004 11:49:46 -0500, Paul DuBois wrote: > Make sure the server really is picking up the option value: > > > SHOW VARIABLES LIKE 'character%'; > > > Look f

Re: MySQL and Unicode (Solved)

2004-04-20 Thread Stormblade
Embarrassing but I blame it on hunger! It's working now. Bottom line was I hadn't restarted the server. Now I know I said I did. Here's where I blame hunger. I was restarted A server. My Tomcat server. I kept restarting it thinking I was restarting the MySQL serverdon't ask. Like I said I blam

Re: MySQL and Unicode

2004-04-20 Thread Paul DuBois
At 13:03 -0400 4/20/04, Stormblade wrote: On Tue, 20 Apr 2004 11:49:46 -0500, Paul DuBois wrote: Make sure the server really is picking up the option value: SHOW VARIABLES LIKE 'character%'; Look for 'character_set_server'. If it's utf8, then perhaps your GUI tools are overriding the settin

Re: MySQL and Unicode

2004-04-20 Thread Paul DuBois
At 11:02 -0400 4/20/04, Stormblade wrote: On Tue, 20 Apr 2004 09:21:00 -0500, Paul DuBois wrote: At 9:38 -0400 4/20/04, Stormblade wrote: On Tue, 20 Apr 2004 11:32:22 +0300, Victoria Reznichenko wrote: Stormblade <[EMAIL PROTECTED]> wrote: Hopefully this will be the last snag...least till the

Re: MySQL and Unicode

2004-04-20 Thread Paul DuBois
At 9:38 -0400 4/20/04, Stormblade wrote: On Tue, 20 Apr 2004 11:32:22 +0300, Victoria Reznichenko wrote: Stormblade <[EMAIL PROTECTED]> wrote: Hopefully this will be the last snag...least till the next one :) I'm having a problem setting the charset to unicode (utf-8). If I understood what I

Re: MySQL and Unicode

2004-04-20 Thread Stormblade
On Tue, 20 Apr 2004 11:32:22 +0300, Victoria Reznichenko wrote: > Stormblade <[EMAIL PROTECTED]> wrote: >> Hopefully this will be the last snag...least till the next one :) >> >> I'm having a problem setting the charset to unicode (utf-8). If I >> understood what I read I can set each table to su

Re: MySQL and Unicode

2004-04-20 Thread Victoria Reznichenko
Stormblade <[EMAIL PROTECTED]> wrote: > Hopefully this will be the last snag...least till the next one :) > > I'm having a problem setting the charset to unicode (utf-8). If I > understood what I read I can set each table to support a charset. But what > I want to do is set the default charset for

Re: MySQL and Unicode

2004-04-09 Thread Warren Young
Pascal Francq wrote: OK, you use a C "char*" using an UTF-8 encoding. That's very commmon in the Unix world. 2-byte encodings are very rare on Unix-like systems, for compatibility reasons. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://li

Re: MySQL and Unicode

2004-04-09 Thread Pascal Francq
OK, you use a C "char*" using an UTF-8 encoding. On Friday 09 April 2004 11:45, Hirofumi Fujiwara wrote: > > Hi, > > I have a question. I have read that since MySQL 4.1, VARCHAR type can > > hold unicode characters. But, it seems that the API of the C library use > > to send queries to the server

Re: MySQL and Unicode

2004-04-09 Thread Hirofumi Fujiwara
> Hi, > I have a question. I have read that since MySQL 4.1, VARCHAR type can hold > unicode characters. But, it seems that the API of the C library use to send > queries to the server still use 'const char*' for the type of the query. > So, praticaly, if I have a unicode string stored in C, how

RE: mysql and unicode ....

2002-06-19 Thread Dean Harding
Not natively (i.e. you can't sort on a Unicode field, for example), but you can still store Unicode text in fields. Just use a BLOB or you can even use VARCHAR(), et al, but remember that you only get half as many Unicode characters as you specify in the field width... If you're using the native