Re: utf8 options under Mysql

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

Re: utf8 options under Mysql

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 in the range of characters they ca

Re: utf8 queries

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, ensure that you set utf8

Re: utf8 problem in index

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

RE: utf8 importing problem

-Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, October 30, 2006 1:05 PM > To: Jerry Schwartz > Subject: RE: utf8 importing problem > > Jerry, > I checked the imported data ( sql file) and the data are in > utf8 coding. > Is th

RE: utf8 importing problem

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 Ave. Farmington,

Re: utf8 still creates broken chars

>Haven't read your issue in its entirety, but UTF-8 can definitely >handle these characters. >The prob is either in the DB, the app, or the tomcat config. > >1. The DB: Make absolutely sure that the content in the db is in fact UTF-8. > >One thing I've done in the past to verify this exact issue, i

Re: UTF8 support in MySQL 4.0

Marco wrote: So how can I do that? There's nothing special you need to do with MySQL itself. Somehow your program obtains UTF-8 data. Insert said data into database. That's it. Perhaps you should read up on UTF-8, to see why this is so. Again, don't expect the database server to be able

Re: UTF8 support in MySQL 4.0

So how can I do that? I've already tried SET CHARACTER SET and it didn't work since someone said its not available in MySQL 4.0. You can store UTF-8 in any database in the world. UTF-8 is compatible with any application capable of dealing with null-terminated strings of 8-bit characters. Tha

Re: UTF8 support in MySQL 4.0

Warren Young wrote: That's why it's possible in the Unix/C world, Typo: should be "That's why it's _popular_..." -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: UTF8 support in MySQL 4.0

Marco wrote: So is there any solution on how I can properly use foreign characters and store them in a MySQL 4.0 database? You can store UTF-8 in any database in the world. UTF-8 is compatible with any application capable of dealing with null-terminated strings of 8-bit characters. That's

Re: utf8, 4.1, and character length truncation in mysql system tables

Hi! Normally, people will choose "lazy" method, define default charset as 'utf8'. But based on the information of mysql, one might be able to define at table level as 'utf-8' instead of whole database charset. In normal case, only certain table or certain "col" might store 'utf-8' data. Hence

Re: utf8, 4.1, and character length truncation in mysql system tables

Hello. > Is there something else I should be doing to create new users post > 4.1? > Is this behavior something I should be worried about? (I am, > currently.) Switch to the latest release (4.1.11). See also: http://dev.mysql.com/doc/mysql/en/user-names.html Adam Fields

Re: utf8, 4.1, and character length truncation in mysql system tables

On Thu, May 12, 2005 at 10:08:33PM +0300, Gleb Paharenko wrote: > Hello. > > > Is this a known issue? > > It is interesting for me. According to the: > > http://dev.mysql.com/doc/mysql/en/charset-metadata.html > > MySQL stores usernames in utf8. Yes, you should convert your > tables to utf8,

Re: utf8, 4.1, and character length truncation in mysql system tables

Hello. > Is this a known issue? It is interesting for me. According to the: http://dev.mysql.com/doc/mysql/en/charset-metadata.html MySQL stores usernames in utf8. Yes, you should convert your tables to utf8, however, in my opinion, you don't have to do this with 'mysql' database. C

Re: utf8 questions?

great, so this is how the mailing list works...ahh... On 4/13/05, Paul DuBois <[EMAIL PROTECTED]> wrote: > Possibilities: > > - option file is not one that is read by mysql > - you didn't put the option in the [mysql] section > - you included the leading dashes. > > If you invoke mysql with the

Re: utf8 questions?

At 9:59 +0800 4/13/05, D. wrote: I don't know if this is the right way to get back to the thread, hopefully this will be placed under the same thread. :) Thank you for your input, Ligaya. ahhh...mbstring, I tired that after i got your reply, but it didn't help to solve the puzzle, I did manage to f

Re: utf8 questions?

I don't know if this is the right way to get back to the thread, hopefully this will be placed under the same thread. :) Thank you for your input, Ligaya. ahhh...mbstring, I tired that after i got your reply, but it didn't help to solve the puzzle, I did manage to find myself a solution last nigh

Re: utf8 questions?

have you altered your php.ini file in the mbstring section? I don't know if it makes a difference but I have always changed my to: ; language for internal character representation. mbstring.language = utf8 ; internal/script encoding. mbstring.internal_encoding = utf8 and have never had a problem

Re: utf8 x latin

Thanks for your help Gabriel. I will use the latin1 with case sensitive. Andre On 1/31/05 7:32 AM, "Gabriel PREDA" <[EMAIL PROTECTED]> wrote: > I think you should use: latin1_general_ci and on columns with spanish you > should use latin1_spanish_ci. > > English, French, Portuguese not having

Re: utf8 x latin

I think you should use: latin1_general_ci and on columns with spanish you should use latin1_spanish_ci. English, French, Portuguese not having a separate collation I believe that they are included into latin1_general_ci ? Please observe the last part from a collation name: case sensitive (_cs) .

Re: Utf8 collations

Brown, Brooks wrote: I ran mysqld with arguments --default-character-set=utf8 and --default-collation=utf8_unicode_ci, and created a table with no collation specification. I didn't test specifically with ç, but e and e-acute were equivalent. For me this is was problem, but it sounds like for you

RE: Utf8 collations

e desired behavior. -Original Message- From: Andrew Nagy [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 01, 2004 11:03 AM To: Brown, Brooks Cc: [EMAIL PROTECTED] Subject: Re: Utf8 collations Brooks, this isn't an answer to your question, but a question to you regarding what yo

Re: Utf8 collations

Brooks, this isn't an answer to your question, but a question to you regarding what you have done. I would like to do a query such as: SELECT title FROM books WHERE title LIKE '%Francais%'; And in return get: +--+ | title| +--+ | Français | +--+ Does the "CHARACTER SET

Re: Utf8 collations

Hi. See: http://dev.mysql.com/doc/mysql/en/Charset-config-file.html "Brown, Brooks" <[EMAIL PROTECTED]> wrote: > All of the unicode collations listed in the reference manual except the = > binary collations are not sensitive to diacritical marks. That is, if I = > do the following: >

Re: UTF8 columns and MySQL

> Hello, > > I have a table with the following column among others: > > text VARCHAR(120) CHARACTER SET utf8 > > The provider I am using however only offers MySQL version 3.23.58, > so I cannot use this statement. At first I thought I was not going > to be able to store UTF8. So I changed the c

Re: UTF8 pre-4.1?

Many thanks, Tim. I don't know to what use they intend to put the strings which they are storing, but I'll pass on this information to the developers with the question. Thanks again, --V Little, Tim wrote: There isn't "support" for it prior to that. But you absolutely can store and retrieve UTF8

Re: UTF8 pre-4.1?

On Thu, Sep 16, 2004 at 10:56:55AM -0700, V. M. Brasseur wrote: > *I* understand that Unicode utf8 support does not happen until version > 4.1 (I can read the manual), but there are some in the office who are > skeptical and somehow believe that there is support for it in earlier > versions (as

Re: UTF8 collations in 4.1.3

> Entering it in hex works for me too. So the problem _was_ actually with > the values I inserted into the database. > > What's the best way to actually see what is stored in the database, > preferably as hex or something else that a terminal is guaranteed to > display correctly? Clearly, what

Re: UTF8 collations in 4.1.3

On Tue, Aug 03, 2004 at 01:11:44PM -0400, Jeremy March wrote: > Is this for Swedish language data? I don't know Swedish so I don't > actually know where u-diaeresis is sorted in Swedish myself, but > according to the source code (in the file: strings/ctype-uca.c) the > u-diaeresis is sorted as an

re: UTF8 collations in 4.1.3

>... > mysql> SELECT col2 FROM test ORDER BY col2 COLLATE utf8_swedish_ci; > ++ > | col2 | > ++ > | M(u-diaresis)ller | > | Muffler| > | MX Systems | > | MySQL | > ++ > ... > I expect M(u-diaeresis)ller to sort after MX Systems in the following:

Re: utf8 - left function

> Problem tested using both version 4.0.18 and 4.1.1 > > This query gets first byte of utf8 character, not two bytes > > If I use > > SELECT LEFT(FieldName, 2) AS FirstLetter, COUNT(*) FROM TableName GROUP BY > FirstLetter > > > gets right utf8 characters but others wrong > > for example; >

Re: utf8 - left function

AIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, March 13, 2004 5:34 AM Subject: re: utf8 - left function > > Hi, > > > > I need this query; > > > > SELECT LEFT(FieldName, 1) AS FirstLetter, COUNT(*) FROM TableName > > GROUP BY FirstLetter >

re: utf8 - left function

> Hi, > > I need this query; > > SELECT LEFT(FieldName, 1) AS FirstLetter, COUNT(*) FROM TableName > GROUP BY FirstLetter > > my datas in utf8 format. I can't get first characters of the datas in > utf8 format but others is ok. > > Any suggestion? > > Thank you It works for me. I'm using the

re: utf8 case insensitive collation, 4.1.1

You're right. The LIKE comparison only works properly with the Latin letters in utf8. MySQL hasn't yet fixed it to work with the rest of Unicode yet. I believe there is a valid LIKE comparison for ucs2. From what I remember, however, it has problems too if you start putting wildcards at the

Re: utf8

Hi! On Dec 16, Igor Zinkovsky wrote: > I can't find in MySQL 4.1.1 documentation anything about > 'character_set_system' variable. It is setted up to 'utf8'. How can I > change it to be able to use russian KOI8-R in mysql client? You cannot change it. But you don't need to either. It is charact

Re: utf8 collations with national symbol's grouping

Sorry :) i see that simbols i've written was converted into ASCII symbols. That is what i need, but in MySQL :). So is there any collation where: a = a-umlaut = a-with-any-other-"fix" ? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://list

Re: utf8 support

"Li, John" <[EMAIL PROTECTED]> wrote: > > Any hint where and how to get mysql 4.1.1? > Official binaries will be available in September at: http://www.mysql.com/downloads/index.html -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored b

RE: utf8 support

Any hint where and how to get mysql 4.1.1? Thanks John -Original Message- From: Jon Haugsand [mailto:[EMAIL PROTECTED] Sent: Monday, August 25, 2003 3:14 AM To: '[EMAIL PROTECTED]' Subject: Re: utf8 support * John Li > MySql 4.1 should have utf8 charset support, I downloa

Re: utf8 support

"Li, John" <[EMAIL PROTECTED]> wrote: > > MySql 4.1 should have utf8 charset support, I downloaded the alpha version > but don't seem to have the utf8.xml file comes with it. > > Any one know how to get the needed charset support files? utf8 is a built in character set. -- For technical supp

Re: utf8 support

* John Li > MySql 4.1 should have utf8 charset support, I downloaded the alpha version > but don't seem to have the utf8.xml file comes with it. > > Any one know how to get the needed charset support files? It looks like a bug. Try version 4.1.1. See e.g.:

Re: utf8 in 4.1 for Windows

"Jon Hancock" <[EMAIL PROTECTED]> wrote: > > I have read in past postings that UTF8 is not yet working with MySQL 4.1 on the > Windows build. > Can anyone verify this? Yes, utf8 was not compiled. It will be fixed in the next release. > If it is not yet working, can anyone give an estimate when

Re: utf8 support

At 23:03 +0200 7/17/03, Yves Goergen wrote: > >2. What about fulltext search on UTF8 strings? Unavailable. Eh? Why should this be a special DB feature at all? Correct me if I'm wrong (I didn't have very much contect with fulltexts yet), but can't I just give mysql an UTF8 string to search in an

Re: utf8 support

On 17 Jul 2003 at 23:03, Yves Goergen wrote: > > >2. What about fulltext search on UTF8 strings? > > > > Unavailable. > > Eh? Why should this be a special DB feature at all? > Correct me if I'm wrong (I didn't have very much contect with > fulltexts yet), but can't I just give mysql an UTF8 stri

Re: utf8 support

> >2. What about fulltext search on UTF8 strings? > > Unavailable. Eh? Why should this be a special DB feature at all? Correct me if I'm wrong (I didn't have very much contect with fulltexts yet), but can't I just give mysql an UTF8 string to search in an UTF8 column (/data)? Shouldn't this wor

Re: utf8 support

At 17:25 +0300 7/13/03, Sagi Bashari wrote: Hello, I would like to know the status of the UTF8 support in MySQL 4.1. I tried to create a table using utf8 charset, and inserting hebrew text into it. it seems like it still treats this text as binary - for example the length() function returns 8 o

Re: utf8 support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Hinz wrote: > Okan, > > >>I want to enable UTF8 support for mysql.Thats why I have installed mysql 4.1 >>on a Win2K server and set the appropriate character set parameter at my.ini >>file. As the mysql service starts, I get the error that mysql

Re: utf8 support

Okan, > I want to enable UTF8 support for mysql.Thats why I have installed mysql 4.1 > on a Win2K server and set the appropriate character set parameter at my.ini > file. As the mysql service starts, I get the error that mysql can not find > the utf8.xml file. > mysqld-opt: File 'D:\mysql\share\c

Re: utf8 support

"Okan CIMEN" <[EMAIL PROTECTED]> wrote: > I want to enable UTF8 support for mysql.Thats why I have installed mysql 4.1 > on a Win2K server and set the appropriate character set parameter at my.ini > file. As the mysql service starts, I get the error that mysql can not find > the utf8.xml file. > >