Hi all,
I'm currently changing our database to utf-8 with the provided OXID script from
this page:
https://www.oxid-esales.com/en/support-services/documentation-and-help/oxid-eshop/installation/oxid-eshop-update-installation/update-eshop-to-utf-8-encoding.html
Now I'm still wondering why we chan
Hi Gregor
only the columns which are supposed to have utf8 content are changed. We
saw no benefit to do this for the id columns. If we would change the id
columns, there could be problems with 3rd party systems or more effort
to update an existing database. But you are right, this behavior is
Hello,
I think this is more related to memory size, latin is a single byte encoding
while utf8 is two byte encoding (any sysadmin/db admin there correct me if I am
wrong?)
The other thing that you should keep all ids the same latin encoding to prevent
type conversion on mysql queries/joins.
-
Hi both of you,
thanks for the information and explanation. Now I understand your thoughts
about the migration to utf8. It’s fine for me just wanted some background
information J
Best regards
Gregor Panek
Softwareentwickler
Marketing/E-Commerce
__
Printus
Hi Gregor,
be careful when using this script, it has a bug that causes your theme and
module settings to disappear: https://bugs.oxid-esales.com/view.php?id=6012
Frank
Von: gregor.pa...@printus.de
Gesendet: Mittwoch, 18. Januar 2017 15:57
An: dev-general@li
Hi Frank,
thanks for the information. Just checked my theme settings on the dev machine
and as you mentioned they are disappeared. Since the bug is still open, what's
the best way to avoid this problem? Has someone an already fixed script? I
think I'm not the only one who wants to switch to utf