Character sets and collations are not reverse engineered

MySql - related issues
Post Reply
gemisigo
Posts: 29
Joined: Thu Mar 07, 2013 1:12 pm

Character sets and collations are not reverse engineered

Post by gemisigo » Mon Mar 25, 2013 8:21 pm

Hi!

Database, table and column character sets and collations are not retrieved during reverse engineering. Also, I see no options for storing those among Schema and Table properties (though the Data Type Suffix and/or Column Definition Suffix could be used for that purpose but that's only valid for columns and it's not very intuitive either).

donose.mihai
Posts: 470
Joined: Thu Apr 07, 2011 11:05 am

Re: Character sets and collations are not reverse engineered

Post by donose.mihai » Fri Apr 12, 2013 9:12 am

i think this issue has been solved.

gemisigo
Posts: 29
Joined: Thu Mar 07, 2013 1:12 pm

Re: Character sets and collations are not reverse engineered

Post by gemisigo » Fri Apr 12, 2013 10:45 am

Thank you very much! I'll check it after the update.

peleus
Posts: 54
Joined: Fri Nov 09, 2012 3:43 pm

Re: Character sets and collations are not reverse engineered

Post by peleus » Sat Apr 20, 2013 6:55 pm

Can the solution please be posted here too?

Grahamfubre
Posts: 20
Joined: Sat Feb 24, 2018 5:58 pm

Character sets and collations are not reverse engineered

Post by Grahamfubre » Tue Mar 06, 2018 1:43 am

The uniEncode and uniDecode functions are deprecated and shouldnt be used with LC 7 or above, though they do still work. But the new functions are much easier to work with and I recommend them. See textEncode and textDecode in the dictionary. They do all the work for you, as long as you know the correct character set youre working with and you do.

Or you can follow AndyPs suggestion, and set the database to use UTF8.

Post Reply