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 <gregor.pa...@printus.de>
Gesendet: Mittwoch, 18. Januar 2017 15:57
An: dev-general@lists.oxidforge.org
Betreff: AW: Database utf8 and latin1 questions

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 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
................................................................................................................................

Von: Tomas Kvietkauskas [mailto:tomas.kvietkaus...@nfq.com]
Gesendet: Mittwoch, 18. Januar 2017 14:53
An: dev-general@lists.oxidforge.org
Betreff: Re: Database utf8 and latin1 questions

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.


-
Tomas


On 18 Jan 2017, at 15:40, Gregor Hyneck 
<gregor.hyn...@oxid-esales.com<mailto:gregor.hyn...@oxid-esales.com>> wrote:


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<mailto: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<http://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
................................................................................................................................



Reply via email to