Re: Text (uni)coding issue

Hmm? did you encode the data correctly as you put it in the db? The data was transmitted from device to server using HostM's MySQL HTTPS API Solution 1.1.3 @ https://www.hostm.com/tutorials/livecode/api-mariadb-mysql (amazing tool and web host). It looks like they are sending as

Re: Text (uni)coding issue

> On 27 Aug 2017, at 11:44 am, Andrew Bell via use-livecode > wrote: > > There were some errors (I think from email translations), but I think I > understand what you're trying to do. The data still seems to be in a weird > format. Hmm… did you encode the data

Re: Text (uni)coding issue

- you need to know your database encoding (let?s assume UTF-8) I was still fairly green to mySQL when I first created this database, so I never changed the default. Looks like the collation is "utf8mb4_unicode_ci". Should that be changed to something else? The server charset is UTF-8

Re: Text (uni)coding issue

Howdy Andrew There’s a few things to deal with here. - you need to know your database encoding (let’s assume UTF-8) - you need to get values out of your database in a way that gives you the binary data rather than strings that the engine has assumed were in native encoding. Use: local

Re: Text (uni)coding issue

Any reason why you're using binfile instead of file if the text isn't encoded? On Sat, Aug 26, 2017 at 8:34 AM, Andrew Bell via use-livecode < use-livecode@lists.runrev.com> wrote: > I have a database on a LiveCode server that I use to track user > interactions in a LiveCode app. It has gotten

Text (uni)coding issue

I have a database on a LiveCode server that I use to track user interactions in a LiveCode app. It has gotten too big to query in LiveCode without timeout errors (the JSON gets mangled because there are now several thousand records), so I'm trying to generate a text file on the server and