2016/04/22 04:49 ... Jigal van Hemert:
It works for a lot of Western European languages very well, but in some
cases there are problems. For Asian languages there are a lot more
problems. For example, 'ß' isn't considered the same as 'ss'.
Well, the former is an sz-ligature, and the latter is a d
Hi,
On 22/04/2016 04:50, Martin Mueller wrote:
MySQL has a bewildering variety of unicode collation choices. Most of them are language specific, but what is
the difference between "utf8-general-ci", "utf8-unicode-ci", and
"utf8-unicode-520-ci." Do they differ i
MySQL has a bewildering variety of unicode collation choices. Most of them are
language specific, but what is the difference between "utf8-general-ci",
"utf8-unicode-ci", and "utf8-unicode-520-ci." Do they differ in the range of
characters they can handle or i
On 8/28/2012 4:49 AM, Johan De Meersman wrote:
...
Guess I'll be fixing it manually (well, sed is my friend) in a mysqldump before
syncing up the second node after it's been upgraded.
There is another method you can use that doesn't require
dump+sed+restore. Convert the column from it's cur
utf8 : utf8_general_ciO=o=Ò=Ó=Ô=Õ=Ö=ò=ó=ô=õ=öoe oz
utf8 : utf8_general_mysql500_ci O=o=Ò=Ó=Ô=Õ=Ö=ò=ó=ô=õ=öoe oz
utf8 : utf8_danish_ci O=o=º=Ò=Ó=Ô=Õ=ò=ó=ô=õ oe=Œ=œ oz
utf8 : utf8_swedish_ciO=o=º=Ò=Ó=Ô=Õ=ò=ó=ô=õ oe=Œ
- Original Message -
> From: "Rick James"
>
> There is a section on German Sharp-s in
> http://mysql.rjweb.org/doc.php/charcoll
> I agree with "dirty".
Yes, seen it, but thank you. I'm not having character set issues, everything is
nicely UTF8.
Eventually they said "Oh, let's add another, compatible, collation".
They were caught between a rock and a hard place.
> -Original Message-
> From: Johan De Meersman [mailto:vegiv...@tuxera.be]
> Sent: Monday, August 27, 2012 7:43 AM
> To: mysql
> Subject: MySQ
27;s kind of dirty.
Any ideas why utf8_unicode_ci doesn't work as expected? The new server version
is 5.5.24-1~dotdeb.1-log.
Thx,
Johan
mysql> set names UTF8;
Query OK, 0 rows affected (0.00 s
Am 18.11.2011 04:31, schrieb Martin Mueller:
> [mysqld]
> init_connect=’SET collation_connection = utf8_general_ci’
> init_connect=’SET NAMES utf8′
> default-character-set=utf8
> character-set-server=utf8
> collation-server=utf8_general_ci
> skip-character-set-client-hands
On Friday, November 18, 2011 at 03:31:44 UTC, martin.muel...@mac.com
confabulated:
> Is it possible to make utf8 the default for all databases and transactions
> in a MySQL installation?
> The current default is Latin1. There is a suggestion on the Web to edit
> the my.cnf fil
Is it possible to make utf8 the default for all databases and transactions
in a MySQL installation?
The current default is Latin1. There is a suggestion on the Web to edit
the my.cnf file as follows
[mysqld]
init_connect=’SET collation_connection = utf8_general_ci’
init_connect=’SET NAMES utf8
cript which analyses the table definitions and uses
the "trick" of two alter table operations (first to the binary
equivalent of the column type and then to the normal type with the utf8
charset) to convert the data to the correct character set.
It would be nice to be able to detect
I can't help but wonder, if you send a string, does that mean you're putting
text in a blob ? Blobs are binary, and thus don't get encoded in the sense
of UTF8 vs Unicode. For a string, you may want a TEXT type column.
On the other hand, if you're indeed trying to insert bi
Thank you for your reply, Janusz.
I appreciate your help.
I have tried making that call before the INSERT statement, but to no avail.
The table collation is set to "utf8 - default collation", and all columns are
set to "Table default".
I am thinking that this problem might
nput please let me know!
-Original Message-
From: Andreas Iwanowski [mailto:namez...@afim.info]
Sent: Tuesday, August 24, 2010 2:48 PM
To: mysql@lists.mysql.com
Subject: BLOB data gets encoded as utf8!
Hello everyone!
I am using an MFC unicode project that uses ODBC to access a MySQL
5.1.
Is the code you use to get the data out in the same charset as the code you
use to put the data in ? Both should ideally also match your database
setting. Have you tried explicitly setting the connection to UTF8 ?
Just swinging in the dark, here, really.
On Sat, Aug 28, 2010 at 8:04 AM, Andreas
l.com
Subject: BLOB data gets encoded as utf8!
Hello everyone!
I am using an MFC unicode project that uses ODBC to access a MySQL
5.1.50 database via the MySQL ODBC 5.1.6 driver.
character_set_connection is set to utf8 (Which I believe is the default
for the driver) One of the tables contains two LON
Hello everyone!
I am using an MFC unicode project that uses ODBC to access a MySQL
5.1.50 database via the MySQL ODBC 5.1.6 driver.
character_set_connection is set to utf8 (Which I believe is the default
for the driver)
One of the tables contains two LONGBLOB columns, and the table default
Hello everyone!
I am using an MFC unicode project that uses ODBC to access a MySQL
5.1.50 database via the MySQL ODBC 5.1.6 driver.
One of the tables contains two LONGBLOB columns, and the table default
charset is utf-8 (since the application is unicode).
However, when inserting into the LONGBLOB
Running this query:
SELECT *
FROM `tbl_people`
WHERE name = 'Davé'
Returns results like:
'Dave'
I've checked my column, table and database and all are set to
utf8_general_ci collation
And I'm also runnig set names 'utf8' before my select statement.
Hi,
On Tue, Jun 8, 2010 at 12:44 AM, Warren Young wrote:
> The Unicode consortium has stated that Unicode will
> never require more than 21 bits per character[*], and 24 bits is the next
> even multiple of 8 up from that.
Maybe off topic, but just curious...If 3 bytes is enough for all
Unicode
On Jun 7, 2010, at 11:44 AM, Warren Young wrote:
> On 6/7/2010 9:57 AM, Ryan Chan wrote:
>> http://dev.mysql.com/doc/refman/5.0/en/charset-unicode.html
>>
>> Since MySQL only support BMP, so in fact 16 bit is needed actually?
>
> I imagine they were thinking they'd extend the support to full Un
On 6/7/2010 9:57 AM, Ryan Chan wrote:
http://dev.mysql.com/doc/refman/5.0/en/charset-unicode.html
Since MySQL only support BMP, so in fact 16 bit is needed actually?
I imagine they were thinking they'd extend the support to full Unicode
in the future and didn't want you to have to dump and re
http://dev.mysql.com/doc/refman/5.0/en/charset-unicode.html
Since MySQL only support BMP, so in fact 16 bit is needed actually?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Export schema
Export data
Change exported schema to utf8
Import schema into new db
Import exported data into new db
Sent via BlackBerry from T-Mobile
-Original Message-
From: Darryle Steplight
Date: Sun, 7 Jun 2009 22:52:22
To: Uma Bhat
Cc: ewen fortune;
Subject: Re: Best way to
.
>> > But suggestions from you guys who have ACTUALLY worked on such a scenario
>> > would help me out the best.
>> >
>> >
>> > Current Database has:
>> > DEFAULT CHARACTER SET - latin1
>> > DEFAULT COLLATION : latin1_swedish_ci
>> >
>> &
lp me out the best.
> >
> >
> > Current Database has:
> > DEFAULT CHARACTER SET - latin1
> > DEFAULT COLLATION : latin1_swedish_ci
> >
> > We need to convert this to
> > DEFAULT CHARACTER SET - utf8
> > DEFAULT COLLATION : utf8_general_ci
> >
>
AULT CHARACTER SET - latin1
> DEFAULT COLLATION : latin1_swedish_ci
>
> We need to convert this to
> DEFAULT CHARACTER SET - utf8
> DEFAULT COLLATION : utf8_general_ci
>
>
> Note that this has to be done on a database that has *existing data* in it .
>
> Hence just by doing
CHARACTER SET - utf8
DEFAULT COLLATION : utf8_general_ci
Note that this has to be done on a database that has *existing data* in it .
Hence just by doing a:
ALTER DATABASE CHARSET=utf8;
would result in unexpected behaviour of the data.
Thanks!
Uma
Have you tried "in boolean mode"?
Santino Cusimano
At 16:30 -0500 20-11-2008, Little, Timothy wrote:
We are using MySQL 5.0.22 on CENTOS/redhat
linux. The table and database character-sets
are all utf8.
We have a database supporting numerous
languages. Of course, full-
We are using MySQL 5.0.22 on CENTOS/redhat linux. The table and database
character-sets are all utf8.
We have a database supporting numerous languages. Of course, full-text works
beautifully with most of the languages.
But Chinese and Japanese are giving us problems, and there is NO reason
I'm still using win2k mysql 5.1
With default databas encoding, I can do querys with bh English and Chinese GB.
But when database encoding is uft8, all the Chinese become question maks.
Any idea about how to mysql work unicode databa? Thanks a lot.
r_set_filesystem | binary |
| character_set_results| latin1 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | /usr/share/mysql/charsets/ |
+--
On 21.11.2007 15:18 CE(S)T, Marten Lehmann wrote:
>> If I recall that correctly, utf8_swedish_ci is the collation to use for
>> european/western european languages. Those Swedish people think they can
>> stand for whole Europe... ;)
>>
>> Not tested my reply, though.
>
> and doesn't work either.
| 3 | opq |
| 8 | taal |
| 6 | taest |
| 7 | toast |
| 5 | täst |
++---+
Java has been designed for and is working with UTF8 for more than 10
years now. But Mysql still doesn't seem to have any clue about UTF8. All
UTF8 extensions just look like dirty hacks to stuff UT
Hello,
default-character-set=latin1_d e
that's not UTF8.
Regards
Marten
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
en Lehmann <[EMAIL PROTECTED]>
Cc: mysql@lists.mysql.com
Enviadas: Quarta-feira, 14 de Novembro de 2007 21:24:47
Assunto: Re: German collation for UTF8 missing
On 14.11.2007 21:43 CE(S)T, Marten Lehmann wrote:
> I want to store my data with UTF8, thus I'm using the utf8 charset for
On 14.11.2007 21:43 CE(S)T, Marten Lehmann wrote:
> I want to store my data with UTF8, thus I'm using the utf8 charset for
> my tables. But which collcation shall I use? I cannot find anything
> appropriate.
If I recall that correctly, utf8_swedish_ci is the collation to us
Hello,
I want to store my data with UTF8, thus I'm using the utf8 charset for
my tables. But which collcation shall I use? I cannot find anything
appropriate.
I cannot use utf8_unicode_ci or utf8_general_ci, because this seems to
treat "Ä" and "A" equally. So I coul
I assume your collation on the database table 'city' is utf8_general_ci
And also check the columns of the database table 'city' to ensure they are also
utf8_general_ci.
The database, its tables, and the tables individual columns can all have a
different collation.
Last, ensu
Hello.
I have a problem with queries on a utf8 table. For example when I send
select SQL_CALC_FOUND_ROWS * from city where country_code = 'pl' and
language_code = 'en' and ( city_name like 'A%' or city_name like "'A%"
) order by city_name
to MySQL, it
Marten Lehmann napsal(a):
Hello,
I have a table like this:
CREATE TABLE `places` (
`name` varchar(256) collate utf8_unicode_ci NOT NULL,
PRIMARY KEY (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci |
Then I want to insert two values:
pjöngjang.com and
pjongjang.com
Hello,
I have a table like this:
CREATE TABLE `places` (
`name` varchar(256) collate utf8_unicode_ci NOT NULL,
PRIMARY KEY (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci |
Then I want to insert two values:
pjöngjang.com and
pjongjang.com
But on the second record I
; > character_set_database values.
> character_set_database is "utf8". The collation utf8_bin slows down
> queries, but is necessary in dealing with multilingual information.
> utf8_general_ci is faster, but can not distinguish in keys between
> symbols which are sorted at the same position
Hi Ananda,
Ananda Kumar schrieb:
>
> So you set the collation_database=utf8_bin, what was your
> character_set_database values.
character_set_database is "utf8". The collation utf8_bin slows down
queries, but is necessary in dealing with multilingual information.
utf8_genera
Hi Harald,
So you set the
collation_database=utf8_bin, what was your character_set_database values.
regards
anandkl
On 8/30/07, Harald Vajkonny <[EMAIL PROTECTED]> wrote:
>
> Harald Vajkonny schrieb:
> > In doing this I got another idea: Does anybody know the difference
> > between the collatio
Harald Vajkonny schrieb:
> In doing this I got another idea: Does anybody know the difference
> between the collations utf8_general_ci, utf8_unicode_ci and utf8_bin?
> I'll try these first and then get back to you about the results.
>
That was it. If I choose utf8_bin as collation everything wor
Dušan Pavlica schrieb:
> What's the charset and collation of your primary field in the table?
With which command do I get the charset and collation information of a
single field in a table? SHOW CREATE TABLE returns:
...
) ENGINE=MyISAM DEFAULT CHARSET=utf8 |
But I believe it is utf8,
Harald Vajkonny napsal(a):
Dušan Pavlica schrieb:
Try to convert file to latin1, if it's possible, create database with
latin1 charset, create table with required structure (you can set utf8
charset to string fields ) and then load data.
I can not convert the file into l
Dušan Pavlica schrieb:
> Try to convert file to latin1, if it's possible, create database with
> latin1 charset, create table with required structure (you can set utf8
> charset to string fields ) and then load data.
I can not convert the file into latin1, because it is mul
Ananda Kumar schrieb:
> strange. did u exit and reconnect and did the select?
>
Yes, I tried it once more. I have to put the USE command before I change
session settings to "latin" to make it work without error (otherwise I
still get the duplicate message). But even after exiting I get the
natio
te message). But even after exiting I get the
national characters displayed as two (or more) bytes.
Try to convert file to latin1, if it's possible, create database with
latin1 charset, create table with required structure (you can set utf8
charset to string fields ) and then load data. Wha
Ananda Kumar schrieb:
> strange. did u exit and reconnect and did the select?
>
Yes, I tried it once more. I have to put the USE command before I change
session settings to "latin" to make it work without error (otherwise I
still get the duplicate message). But even after exiting I get the
nati
llation, I
> get the data loaded correctly into the database without error msg, but
> when I want to display it with "SELECT * from table" I don't get it
> displayed correctly, even after I change the settings back to utf8 after
> the import.
>
> Best regards,
> H.
>
ange the server settings by adding the
following lines in the [mysqld] section of my /etc/my.cnf:
collation_server=utf8_unicode_ci
character_set_server=utf8
skip-character-set-client-handshake
Now the server also runs with utf8, but when loading the file, I still
get the same error message
displayed correctly, even after I change the settings back to utf8 after
the import.
Best regards,
H.
--
"Wouldn't the sentence 'I want to put a hyphen between the words Fish
and And and And and Chips in my Fish-And-Chips sign' have been clearer
if quotation marks had been
back to you all.
regards
anandkl
On 8/30/07, Dušan Pavlica <[EMAIL PROTECTED]> wrote:
>
> Edward Kay napsal(a):
> >> I would like to import data from a utf8-coded comma seperated file. I
> >> created my database with "DEFAULT CHARACTER SET utf8 COLLATE
>
Edward Kay napsal(a):
I would like to import data from a utf8-coded comma seperated file. I
created my database with "DEFAULT CHARACTER SET utf8 COLLATE
utf8_general_ci" and I started my mysql-client with the
--default-character-set=utf8 option. Nevertheless, when I input primary
Edward Kay schrieb:
> Try using the SET NAMES 'utf8' statement [1] to tell MySQL that your client
> is sending data in UTF-8. I believe that as your server is latin1, it will
> assume this is the character set used by the command line client.
>
> [1] http://dev.mysql.com/
> I would like to import data from a utf8-coded comma seperated file. I
> created my database with "DEFAULT CHARACTER SET utf8 COLLATE
> utf8_general_ci" and I started my mysql-client with the
> --default-character-set=utf8 option. Nevertheless, when I input primary
> key
Ananda Kumar schrieb:
> Before you import at the mysql prompt set below variables and then try
> again to load
>
> set session max_error_count=50;
> set session collation_database=latin1_swedish_ci;
> set session character_set_database=latin1;
This is not what I need, bec
;
> Hello,
>
> I would like to import data from a utf8-coded comma seperated file. I
> created my database with "DEFAULT CHARACTER SET utf8 COLLATE
> utf8_general_ci" and I started my mysql-client with the
> --default-character-set=utf8 option. Nevertheless, when I inp
Hello,
I would like to import data from a utf8-coded comma seperated file. I
created my database with "DEFAULT CHARACTER SET utf8 COLLATE
utf8_general_ci" and I started my mysql-client with the
--default-character-set=utf8 option. Nevertheless, when I input primary
key fields, which d
On 10 jun 2007, at 20.47, tAndRead wrote:
Hi all,
when I try to add a foreign text from the keyboard in the mysql
client,
keystrokes are ignored! unless they are numbers, commas etc
(using kde-konsole with the the DeJaVu international font)
I believe this has to do something with the co
Hi all,
I have compiled mysqld 5.0.37 with utf support:
( configure --with-charset=utf8 --with-extra-charsets=none)
utf8 is the default in my.cnf:
( [mysqld] character-set-server=utf8 and [mysql] default-character-set=utf8 )
mysqld acknowledges it:
mysql> show variables like &quo
Hi all,
I have compiled mysqld 5.0.37 with utf support:
( configure --with-charset=utf8 --with-extra-charsets=none)
utf8 is the default in my.cnf:
( [mysqld] character-set-server=utf8 and [mysql] default-character-set=utf8 )
mysqld acknowledges it:
mysql> show variables like &quo
Hello,
Is it possible to restaure a .sql file encoded in utf8 to mysql with
mysql client set to latin1?
I've got a forum on a server which has got it's client set to utf8
I need to move the forum to a new server. But this new server has got
postfix and proftp that seem to need
Remember that my MySQL skills are at the beginner level; and this whole
Unicode / utf8 business always gives me a headache.
Any Unicode or utf8 characters with diacritical marks will look funky in
DOS.
Normally what I do is take my data, convert it from uft8 to utf8, and see if
the results match
Most likely the UTF8 is still in the data base, but whatever program you are
using to view it is not displaying UTF8 properly. MySQL's command line
program will not, for example, even if you SET NAMES "utf8".
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington
I use MySQL database with utf8 character set and utf8_czech_ci
collation.
It works well on Linux server but when I try to
export the data and import into the same database but running on XP machine the
utf8 is
gone.Instead of a proper coding there are some strange characters.
I used
is - there's a great utility
>auto_ef [auto encoding finder].
>
Michael, thanks for the tip. At the command line, I entered:
mysql -uroot -p --default-character-set=utf8 recruitment_play -e "select
mainbody from advert where vacancyid = 428" > output.txt
This is what showe
Hi,
I thought my utf8 settings on my database and tomcat were effective, but I am
still getting ? characters instead of the real thing, even for simple things
like latin extended-A, and even some latin-1 characters are broken. Any ideas?
Here is some text as entered, and as returned by my
Hello,
I am trying to install php nuke and I get this error:
File 'c:\mysql\share\charsets\?.conf' not found (Errcode: 2)
Character set '#33' is not a compiled character set and is not specified in
the 'c:\mysql\share\charsets\Index' file
I have researched it and nothing ive tried works.
Any
create index ub_city_key on ub (city(3));
id: 1
select_type: SIMPLE
table: ub
type: ref
possible_keys: ub_id_key,ub_city_key
key: ub_city_key
key_len: 11
ref: const
rows: 4340
Extra: Using where
1 row in set (0.00 sec)
Why
2 bytes ?
- is there something special about clustered tables in that it
treats all char data as utf8 charsets ?
- is my test invalid in that the Microsoft encoding for the Korean
characters only needs 1 byte ?
Thanks for any replies,
Yong.
How are you importing the dump into mysql? Importing by piping the dump
file to mysql may broke some chars due to shell.
Have you tried this: (with in mysql client)
SET NAMES UTF8; SET CHARACTER SET UTF8
source /pathto/dump.sql
Cheers,
--Ravi
Sean O'Hara wrote:
Hi All,
I've bee
Hi All,
I've been googling all morning trying to find info on how to do a
mysqldump of a utf8 encoded database from which I can restore without
corrupting all the non ascii characters. If anyone has any pointers
on this, I'd be most grateful.
Here is my setup. I am building
Any ideas on whether and when MySQL is likely to support 4 byte utf8
sequences?
Chris Key
MySQL list,
I have a database on a server that contains English and Japanese text. I
have tried to ensure at every turn that all text encoding is in utf8.
On the web hosting server where the live site resides, everything is
working fine.
But on my testing environment at home, the Japanese
e and Spanish. All the pages and PHP scripts are in
UTF8, and I've been using the PHP function utf8_decode() before
recording strings in the db because MySQL 3 doesn't support UFT8.
Similarly I've been using utf8_encode() after reading them and
outputting them to the web.
It&
Hi all,
I’m working in a project that use MySQL.
The data is Vietnamese.
So, I have used MS Access 2003 to test displaying this data.
I have configured ODBC Initial Statement Option as “set names utf8”, and use MS
Acccess link to the database.
But, the data can’t display correctly.
I’m
Grzegorz Smith wrote:
Hi all. In my apps I use two languages: english and my national polish.
Translates i keep in MySQL 5.0 in text field (MyISAM engine) with utf8
encodings. I don't know why but i can get polish translates from databes
properly, my national character are seen from webb
p in MySQL 5.0 in text field (MyISAM engine) with utf8
> encodings. I don't know why but i can get polish translates from databes
> properly, my national character are seen from webb like sign ?. I connect
> to database with URI like
> host://[EMAIL PROTECTED]:database?read_default_
Hi all. In my apps I use two languages: english and my national polish.
Translates i keep in MySQL 5.0 in text field (MyISAM engine) with utf8
encodings. I don't know why but i can get polish translates from databes
properly, my national character are seen from webb like sign ?. I conne
, moreover I placed
into brackets the UTF8 codes that should be used normally instead of them.
C383C2A1 (C3A1) LATIN SMALL LETTER A WITH ACUTE
C383C2A9 (C3A9) LATIN SMALL LETTER E WITH ACUTE
C383C2AD (C3AD) LATIN SMALL LETTER I WITH ACUTE
C383C2B3 (C3B3) LATIN SMALL LETTER O WITH ACUTE
C383C2B6 (C3B6
the UTF8 codes that should be used normally instead of them.
C383C2A1 (C3A1) LATIN SMALL LETTER A WITH ACUTE
C383C2A9 (C3A9) LATIN SMALL LETTER E WITH ACUTE
C383C2AD (C3AD) LATIN SMALL LETTER I WITH ACUTE
C383C2B3 (C3B3) LATIN SMALL LETTER O WITH ACUTE
C383C2B6 (C3B6) LATIN SMALL LETTER O WITH
Hello.
Start from reading this part of the manual:
http://dev.mysql.com/doc/refman/5.0/en/charset.html
> From my understanding, the database itself never do any conversion,
> meaning if you insert utf8 data into tables declared as latin1 it
> doesn't really matter if you retrie
Hi list,
I guess this is a classic problem...!
I found that on the web: http://www.oreillynet.com/pub/wlg/9022?wlg=yes,
where basically the guy did " dump data, change the charset in the table
definition and reinsert the records into an utf8 database" and ended up with
some probl
convert the special characters with UTF8 but I don't know how
> to write the SQL-query to insert data in the following table:
>
> CREATE TABLE `books`
> (
> `id` int(11) NOT NULL auto_increment,
> `txt` text character set latin1 NOT NULL,
>PRIMARY KEY (`id`),
>
Hi list,
I'm having some problems while trying to save into a TEXT field some data
containing text and special characters from a C program!
I thought to convert the special characters with UTF8 but I don't know how
to write the SQL-query to insert data in the following table:
CREATE TA
ation is same
>
>
> mysql> SELECT VERSION();
> +-+
> | VERSION() |
> +-+
> | 5.0.18-standard-log |
> +-+
> 1 row in set (0.01 sec)
>
> mysql> SET NAMES utf8;
> Query OK, 0 rows affected (0.00 s
18-standard-log |
+-+
1 row in set (0.01 sec)
mysql> SET NAMES utf8;
Query OK, 0 rows affected (0.00 sec)
## I tried to make function tokyo() which returns string 'Tokyo' in
## Japanase. _utf8 X'E69DB1E4BAAC' means Tokyo in Japanese.
mysql> DELIMITER //
mysql
What is the best (most optimal) way to perform a case-insensitive search
for a VARCHAR column with COLLATE utf8_bin?
I'm assuming the answer is not:
SELECT *
FROM MyTable
WHERE UPPER(MyColumn) LIKE Upper('%pattern%');
Tia!
R.
--
MySQL General Mailing List
For list ar
wangxu wrote:
> I can't operate utf8 characters within command-line in linux operating system.
> Mysql doesn't support?
I can enter utf8 characters using the mysql command-line client just
fine -- SuSE 9.1, MySQL 4.1.13 on this system.
FWIW!
--
hen read http://dev.mysql.com/doc/refman/4.1/en/installing-source.html and
> add the two options to the configure.
>
> > > I can't operate utf8 characters within command-line in linux operating
> > > system. Mysql doesn't support?
> >
> > --without-lib
Follow is the result.
+--+-+
| Variable_name| Value |
+--+-+
| character_set_client | utf8
eichardt" <[EMAIL PROTECTED]>;
Sent: Tuesday, December 20, 2005 11:47 AM
Subject: Re: insert utf8 character in Linux commind-line tool
> export LANG=zh_CN.UTF-8
> - Original Message -
> From: "wangxu" <[EMAIL PROTECTED]>
> To: "Andreas Streichard
Hello.
Please, provide the output of this statement:
show variables like '%char%';
> I import utf8 character in terminal commind-line is well.So in my
>word,there aren't error in my terminal settings.
>
--
For technical support contracts, goto https://ord
on...
then read http://dev.mysql.com/doc/refman/4.1/en/installing-source.html and
add the two options to the configure.
> > I can't operate utf8 characters within command-line in linux operating
> > system. Mysql doesn't support?
>
> --without-libedit –with-readline=/us
export LANG=zh_CN.UTF-8
- Original Message -
From: "wangxu" <[EMAIL PROTECTED]>
To: "Andreas Streichardt" <[EMAIL PROTECTED]>;
Sent: Tuesday, December 20, 2005 10:10 AM
Subject: Re: (瑞星提示-此邮件可能是垃圾邮件)Re: insert utf8 character in Linux commind-line
tool
1 - 100 of 226 matches
Mail list logo
