, 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 programs out there.
>>
>> I now
use-livecode:
>> 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, s
-livecode:
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
an'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 uft8mb4 (4 byte
> chars), which LiveCode obviously doesn't like and can't display anymore the
>
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
> of AWS restrictions.
>
> In this context I am doing tests and also tried to see what my programs
> (LiveCode > PHP > mySQL) say about mySQL 8.
>
> For this I imported a current 5.6 dump into a mySQL 5.7 and into a 8.0 test
> DB.
>
>
>
> With mySQL 5.7
Hello folks,
I have a DB hosted on AWS and need to move it from mySQL 5.6 to 5.7 because
of AWS restrictions.
In this context I am doing tests and also tried to see what my programs
(LiveCode > PHP > mySQL) say about mySQL 8.
For this I imported a current 5.6 dump into a myS
