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 a
little bit inconsistent and you have to keep it in mind.
Kind regards
Gregor Hyneck
Software Developer
OXID eSales AG
Bertoldstraße 48
79098 Freiburg
Deutschland
Vorstand: Roland Fesenmayr (Vorsitzender)
Vorsitzender des Aufsichtsrats: Michael Schlenk, Sitz: Freiburg
Amtsgericht Freiburg i. Br., HRB 701648, USt-IdNr.: DE231450866
Am 18.01.2017 um 13:15 schrieb gregor.pa...@printus.de:
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 change everything to utf8 except the ID
Columns which are still latin1 encoded? What’s the reason behind this?
Can someone explain this? In my opinion this is a little bit
inconsistent and generates additional work when creating new tables
because you have to keep in mind to set the encoding for the ID
Columns as latin1.
Best regards
Gregor Panek
Softwareentwickler
Marketing/E-Commerce
__________________________________________
Printus GmbH
Carl-Zeiss-Strasse 1, D - 77656 Offenburg
Phone: +49 781 607-498, Fax: +49 781 607-265
gregor.pa...@printus.de <mailto:gregor.pa...@printus.de>
www.printus.de
………………………………………………………………………………………………………………..
Printus – Der Film: Werfen Sie einen Blick hinter die Kulissen von
Printus: www.printus.de/film <http://www.printus.de/film>
Besuchen Sie uns bei Facebook: www.facebook.com/PrintusGmbH
………………………………………………………………………………………………………………..
