mySQL and accented chars revisited

Peter Haworth pete at
Wed Nov 4 20:26:20 EST 2015

Kay's right. You can define the encoding to be used in an SQL database and
utilities should observe that encoding by default.

I added that in the last release of my SQLiteAdmin program, although I also
included preferences to not encode/decode and/or specify an encoding.
That's necessary because the database libraries don't (and can't) check if
the data they are handed is in the correct encoding so in the immortal
words of Forest Gump's mother, "you never know what you're gonna get".

lcSQL Software <>
Home of lcStackBrowser <> and
SQLiteAdmin <>

On Wed, Nov 4, 2015 at 5:16 PM, Kay C Lan <lan.kc.macmail at> wrote:

> On Thu, Nov 5, 2015 at 8:59 AM, John Dixon <dixonja at> wrote:
> > I have just had a thought... How would you go about handling accented
> > chars if you were put in the position of using a mySQL database,
> belonging
> > to someone else,  that had never seen liveCode before ?
> >
> > The same still applies. If any db Admin utility can look at the mySQL db
> and the data appears correctly, then if you textDecode data you SELECT then
> it will appear in your LC app correctly. If you textEncode the data before
> you UPDATE or INSERT it back into the mySQL db then it will appear
> correctly in all those other db Admin utilities.
> Basically these other db Admin utilities should have been written to do the
> equivalent of what you are required to do in LC. They should decode the
> data for presentation on their particular platform - Win, Mac, Linux, and
> encode any data they put back in.
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the use-livecode mailing list