On Aug 24, 2011, at 2:14 PM, Alexander Reichstadt wrote: > 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.
I think you’re going to need to get some Unicode references and look at the exact UTF-8 byte sequences that are being generated as commands to MySQL. (You should also verify that the connection to MySQL is actually expecting UTF-8 and not some other encoding.) If you can figure out what’s wrong with the data being sent, you’ll have an idea of how to fix it. I think it’s very unlikely there is an actual Foundation bug here, as this is really a pretty ordinary usage of NSString. —Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
