> easily solved by changing the structure in the back end table. Probably. I seem to recall trying this years ago, and I had to re-import already imported UTF8 data (like the demo data). Still you have to modify entity.properties and my.cnf so new data will render properly.
On Sun, Apr 2, 2017 at 1:52 PM, Chris Clark <[email protected]> wrote: > I still say this should be easily solved by changing the structure in the > back end table. > > On Apr 2, 2017 3:44 PM, "Mike" <[email protected]> wrote: > > > Great.... Incidentally, I have no idea why the default for mysql, > *STILL*, > > for ofbiz, is not UTF8. Any modern database should, by default, be UTF8 > > compliant. The reason why the ofbiz multi-language demo works be because > > the backend is PostgreSQL. If the same demo data was hosted by mysql, the > > demo wouldn't even work with the defaults in entity.properties. > > > > Committers: Please justify this. > > > > Converting to postgresq? > > > > https://wiki.postgresql.org/wiki/Converting_from_other_ > > Databases_to_PostgreSQL > > > > On Sun, Apr 2, 2017 at 10:29 AM, Ingo Wolfmayr <[email protected]> > > wrote: > > > > > Thanks, that fixed it. > > > > > > I am working on moving to postgresql. Did you move an existing > > ofbiz-mysql > > > database to postgresql? If yes, what was your way of doing it if I may > > ask? > > > > > > -----Ursprüngliche Nachricht----- > > > Von: Mike [mailto:[email protected]] > > > Gesendet: Samstag, 1. April 2017 01:10 > > > An: user <[email protected]> > > > Betreff: Re: Special char > > > > > > I had this exact same problem back when I was using mysql. This is > how I > > > finally got mysql to properly render UTF8 > > > > > > entity.properties > > > character-set="utf8" > > > collate="utf8_general_ci"> > > > jdbc-uri="jdbc:mysql:// > > > 10.2.10.101/ofbiz?autoReconnect=true;characterEncoding=UTF-8" > > > > > > Also: > > > my.cnf > > > character-set-server=utf8 > > > default-collation=utf8_unicode_ci > > > > > > Then (I believe) you have to re-create the database to pick up the UTF8 > > > stuff and reload the UTF8 data. There may be a way to convert an > > existing > > > DB on the fly to UTF8... However: > > > > > > The data in the DB is not UTF8 so you are (most likely) screwed. THIS > is > > > exactly why I ditched mysql and went with postgresql, where everything > is > > > UTF8 by default. > > > > > > On Fri, Mar 31, 2017 at 2:39 AM, Ingo Wolfmayr < > [email protected]> > > > wrote: > > > > > > > Hi everybody, > > > > > > > > I have a question regarding special chars: > > > > > > > > Environment: Ofbiz trunk, Mysql 5.6 > > > > Entity Engine: collate="utf8_unicode_ci", jdbc-uri="jdbc:mysql:// > > > > localhost/ofbiz_test?autoReconnect=true&characterEncoding=UTF-8" > > > > > > > > I have the following strings: > > > > 1) Käse > > > > 2) Akrapovič > > > > > > > > The first one is working. The second becomes Akrapovi? > > > > > > > > Both strings work in the online demo. Does anyone has an idea what I > > > > may do wrong? > > > > > > > > Best regards, > > > > Ingo > > > > > > > > > >
