#29 UTF8 content bug on Intel with 0.7b5

[Tobias Munk]

Hi,

we ran into a really weird bug, confirmed with OS X 10.4 and 10.5.

I am running 0.7b5 on a MacBook Pro (Intel).
I set my default encoding to UTF8.

Now when I start CocoaMySQL and select a table which has special chars in certain fields. In my example here: Ø or 'Ø'.
I see only "NULL" values for the corresponding fields. And also when changing a value in the row. The field containing a special char will be overwritten with "NULL" - very bad :(

This bug does not occur when reselecting UTF8 from the lower left dropdown. I also found out that Macs with PPC processor do not have this bug. And last but not least this bug does not exist in 0.7b4.

Best regards,
schmunk.

PS: Tested with MySQL 5.

[Chris Stainthorpe]

Logged In: YES
user_id=1995836
Originator: NO

Replicated with 0.7b5 on an Intel Mac Mini against MySQL 5.0.37

[Mark Townsend]

Can I have a step by step on how to replicate this problem?

[Tobias Munk]

I'll try a step by step instruction ;)

1. Get an intel-based Mac
2. Open CocoaMySQL 0.7b5
3. Set "default-encoding" to UTF-8
4. Close CocoaMySQL
5. Open CocoaMySQL
6. Select a db and a table
7. Insert a "special char", i.e. 'Ø' into a VARCHAR field.
8. Apply changes

Can you reproduce this?