That's good to hear, I haven't looked into it or tested it for years (and have only had latin-using clients using MySQL in recent years). BTW, about UTF-8: the accepted standard has nothing to do with how MySQL used to support it, and in MySQL if you set the character set to unicode you'd get 3 bytes used for each character, even for ASCII characters. Yeah, it was really bad...
So, it's good to hear they changed that, I've been wondering when it would happen. I'll admit, I'm still not a fan of MySQL. If they would fix the issues with Timestamp millisecond resolution and a few transaction handling things they'd be on their way to being a useful database where you don't have to work around or ignore stuff on a daily basis. Maybe it'll happen sooner or later. Working with MySQL has historically been a pain as they've been slow to move toward being a more enterprise app friendly database (as opposed to a LAMP stack component). -David On Feb 26, 2011, at 3:48 PM, Paul Foxworthy wrote: > Hi all, > > From http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html > http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html : > > "MySQL interprets length specifications in character column definitions in > character units. (Before MySQL 4.1, column lengths were interpreted in > bytes.)" > > MySQL 4.1 production release was in 2004. > > From http://dev.mysql.com/doc/refman/5.0/en/charset-unicode.html > http://dev.mysql.com/doc/refman/5.0/en/charset-unicode.html : > > "utf8, a UTF-8 encoding of the Unicode character set using one to three > bytes per character" > > UTF-8 doesn't require three bytes per character. It has the tremendous > virtue (at least if you happen to speak a language of Western Europe) that > plain ASCII is already in UTF-8 format. You can store any Unicode character, > and you only pay the price in increased storage size for the non-ASCII > characters. > > If that's the only problem, I humbly suggest the default encoding should be > changed to UTF-8. > > Cheers > > Paul Foxworthy > > > David E Jones-4 wrote: >> >> >> On a side note, the only reason this isn't the default in OFBiz is that if >> you use UTF-8 the size of each text column will be reduced to 1/3 of its >> specified size because each UTF-8 character requires 3 bytes in MySQL, and >> the size of a column in MySQL is in terms of bytes, and not in terms of >> characters. Every other DB in the world (that I'm aware of) uses >> characters for column size, MySQL is just weird. >> >> -David >> >> >> On Feb 25, 2011, at 1:51 PM, Mike wrote: >> >>> As I recall (I use postgres now), I had trouble getting multi-language >>> support to work properly in mysql until I made the following changes >>> to entityengine.xml. >>> >>> The default config shows this: >>> >>> character-set="latin1" >>> collate="latin1_general_cs" >>> >>> I believe I had to change the above to: >>> >>> character-set="utf8" >>> collate="utf8_general_ci" >>> >>> When I did the above, I was able to support a multi-language >>> environment...i.e, write product info in multiple languages. >>> Something to think about. >>> >>> >>> On Fri, Feb 25, 2011 at 12:04 PM, Erwan de FERRIERES >>> <[email protected]> wrote: >>>> Le 25/02/2011 11:43, adnane a écrit : >>>>> >>>>> Hello >>>>> >>>>> Thns every body,but i want know how could i creat datasource in the >>>>> file >>>>> entityengine.xml because i notice that this file contain just the >>>>> defenition >>>>> of each data base and in the top of file,we precise wich data base we >>>>> use,so,if i would like use mysql database,sould i change derby and put >>>>> my >>>>> sql or there is on other thing to do?? >>>>> >>>>> Thnks >>>> >>>> Configure your entityengine.xml file: >>>> put the right definition for your mysql database, and choose for the >>>> default >>>> delegator to use the modified datasource. >>>> >>>> https://cwiki.apache.org/confluence/display/OFBTECH/Apache+OFBiz+Technical+Production+Setup+Guide#ApacheOFBizTechnicalProductionSetupGuide-DatabaseSetup >>>> >>>> Cheers, >>>> -- >>>> Erwan de FERRIERES >>>> www.nereide.biz >>>> >> >> >> > > > -- > View this message in context: > http://ofbiz.135035.n4.nabble.com/data-base-tp3323306p3326419.html > Sent from the OFBiz - User mailing list archive at Nabble.com.
