I did something similar. I created a client-server library. The client encrypts
using a unique method that only I know, and the server decrypts using the same
method. This way you can have secure traffic without HAVING to go through a web
server and all the hoopla that involves (for the
Folks,
I have posted a sample php file that I have used for a couple of years, that
uses aes-256 encryption for database operations. Data is encrypted in Livecode
and decrypted by the php script, which posts it to the mysql db. Perhaps it
will be of interest and I welcome any feedback.
I always use UTF8MB4 for all.
If you use phpmyadmin you can change everything on the spot.
UTF8MB4 works great with LC, it's just you need to encode and decode
correct in LC when you send or retrieve data.
I always use PHP files as middleware. So LC sends to the PHP file, and
the PHP file
Hi Tiemo,
Could you use a substitution table as a work around patch?
Rick
> On Jul 8, 2021, at 8:45 AM, Tiemo via use-livecode
> wrote:
>
> Thank you Matthias,
>
> because it is an existing db and years old LC programs in different versions
> out at the customers, I can't modify my old LC
Thank you Matthias,
because it is an existing db and years old LC programs in different versions
out at the customers, I can't modify my old LC programs out there.
I now have read that uft8 gets deprecated in mySQL 8 at some time, so that all
new and migrated mySQL 8 databases gets by default
