Hi Sreenivasulu,
Try to remember to use "Reply All" and keep your replies on list (^_^) There are many here who are much better versed in MySQL than I am. They will probably be able to offer more insight than I am able to provide alone.
Does a case sensitive fetch *really* work?? I believe the ci in utf8_general_ci stands for 'case insensitive.' The number one search result for "utf8_general_cs" gives me:
So it looks like you need to switch over to utf8_bin to get something resembling case sensitivity.
As for a case insensitive search, by default all MySQL queries are case insensitive. If you do a case insensitive query in WO, the plugin for MySQL handles this by converting your query string using UPPER.
Ramsey On Feb 23, 2011, at 10:11 PM, Sreenivasulu A wrote: Hi Ramsey,
It fails to fetch for all three languages.
I didn't change the default collation.
It is,
Collation:
=======
collation_connection: utf8_general_ci
collation_database: latin1_swedish_ci
collation_server: latin1_swedish_ci
Charset:
=======
| character_set_client | utf8 | | character_set_connection | utf8 | | character_set_database |
latin1 | | character_set_filesystem | binary | | character_set_results | utf8 | | character_set_server | latin1 | | character_set_system | utf8 |
But If i execute the eo generated sqls in the database through Toad, it fetches records from database properly.
Will utf8_general_ci is a problem for getting zero records from eomodeld?
If it is a problem, which collation I have to be use to get proper result from eo fetch?
Thanks,
Sreenivasulu Arveti.
On Wed, Feb 23, 2011 at 10:46 PM, Ramsey Gurley <email@hidden> wrote:
> Have you changed MySQL's default collation to a case sensitive utf8 collation? Does it fail in all three languages or just for the non-english fetches?
>
> Ramsey
>
> On Feb 23, 2011, at 9:48 AM, Sreenivasulu A wrote:
>
>> Hi Ramsey,
>>
>> Case sensitive fetch is working properly.
>> I am using MySQL Database.
>>
>> Thanks,
>> Sreenivasulu Arveti.
>>
>>
>>
>> On Wed, Feb 23, 2011 at 10:05 PM, Ramsey Gurley <email@hidden> wrote:
>>> Hi Sreenivasulu,
>>> Not really sure... All other things being equal, does a case sensitive fetch
>>> work? Also, what DB are you using?
>>> Ramsey
>>> On Feb 23, 2011, at 2:14 AM, Sreenivasulu A wrote:
>>>
>>> Hi All,
>>>
>>> I am implementing internationalization in my example application.
>>> For doing this, I kept Schema is in utf-8.
>>>
>>> Entitiy in EOModeled as shown below:
>>>
>>> {
>>> attributes = (
>>> {
>>> allowsNull = N;
>>> columnName = id;
>>> name = id;
>>> precision = 10;
>>> prototypeName = "a_id";
>>> },
>>> {
>>> columnName = "student_name";
>>> name = "student_name";
>>> prototypeName = "a_text";
>>> userInfo = {
>>> ERXLanguages = ("en_us", "ms_my", "zh_cn");
>>> };
>>> valueType = E;
>>> width = 255;
>>> }
>>> );
>>> attributesUsedForLocking = (id, "student_name");
>>> className = Student;
>>> classProperties = ("student_name");
>>> externalName = student;
>>> fetchSpecificationDictionary = {};
>>> name = Student;
>>> primaryKeyAttributes = (id);
>>> }
>>>
>>> All these are working properly. Reading from, writing to Schema is working
>>> properly for english, malay and chinese languages.
>>>
>>> But caseInsensitive eo fetch is not giving result on 'student_name column'.
>>>
>>> If the 'valueType = S' then it is giving proper result, but writing data to
>>> Schema(DB) is not working.
>>>
>>> If the 'valueType = E' then writing data to Schema is working, but
>>> caseInsensitive fetch is fail to give proper result.
>>>
>>> Any help could be greatly appreciated.
>>> Thanks in advance,
>>> Sreenivasulu Arveti.
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>>
>>> This email sent to email@hidden
>>>
>
>
|