Re: Representation of strings with special chars
Re: Representation of strings with special chars
- Subject: Re: Representation of strings with special chars
- From: Alexander Reichstadt <email@hidden>
- Date: Wed, 24 Aug 2011 23:14:39 +0200
It seems a work-around is to append a space to the select-statement, mysql does not care about that and it brings the umlaut-problem to cease in select-statements. Does this only cover some other issue that is going to return, or is this valid? I found a thread talking about the length with umlauts being not clear to answer in some cases which lead me to try this. It doesn't seem like a feature, but I wouldn't know what to log a bug against.
In this context I also observed some bug in Xcode. Using opt-arrow in a text to move through the text in Cocoa apps allows to skip an entire word, not only a single character. But skipping over somewordAÜsomeotherwordB will not bring the cursor from before the s to after the d, but instead hop from s to after A to after Ü to after B.
Am 24.08.2011 um 22:24 schrieb Alexander Reichstadt:
> Actually it's a couple of wrapper-classes to MYSQL c-calls by Karl Kraft.
>
> In the sqlfetch-class, eventually it arrives at....
>
> mysql_stmt_prepare(myStatement, [s UTF8String],[s length])
>
> where s is the NSString instance containing the SELECT-statement, such as SELECT field="someÜberthing".
>
> From there it goes on to....
>
> int STDCALL mysql_stmt_prepare(MYSQL_STMT *stmt, const char *query,
> unsigned long length);
>
>
> ....and at this point it fails.
>
>
>
>
>
>
>
> Am 24.08.2011 um 20:15 schrieb Sean McBride:
>
>> On Wed, 24 Aug 2011 20:07:40 +0200, Alexander Reichstadt said:
>>
>>> Reason to ask and problem to solve is, that the values with Umlauts are
>>> to be passed on to an SQL backend, and in some cases the umlauts are not
>>> forwarded correctly. Escaped they return no answer or, even worse, cause
>>> an SQL error and the sql connection to break. Also escaping the umlauts
>>> int he sql connection does not work.
>>
>> I'm assuming your SQL backend does not understand NSString. How do you convert from NSString, and to what do you convert? Which text encoding is your backend expecting?
>>
>> --
>> ____________________________________________________________
>> Sean McBride, B. Eng email@hidden
>> Rogue Research www.rogue-research.com
>> Mac Software Developer Montréal, Québec, Canada
>>
>>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden