Installing clean new in MySQL 5.5.9
Locked
Installing clean new in MySQL 5.5.9
 
|
I have just setup a brand new install on a machine with Windows 7 32 bit +
MySQL 5.5.9 After creating the databases and granting privileges to the user and password named in the entityengine.xml file I ran the command: "ant run-install-seed" from the directory where ofbiz 10.04 OOTB is installed - This install worked fine with MySQL 5.1. I get the following error back (actually tons of these errors) [java] Error was: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE InnoDB CHARACTER SET latin1 COLLATE latin1_general_cs' Has anyone seen this before? Dead in the water at this point Thanks James |
|
|
You probably want to dump the latin1 character set and use UTF8. If
you use latin1, you can forget about getting a multi-language capable ofbiz installation (I learned the hard way). Try these: table-type="InnoDB" character-set="utf8" collate="utf8_general_ci"> On Wed, Mar 9, 2011 at 10:58 AM, James Lawton <[hidden email]> wrote: > I have just setup a brand new install on a machine with Windows 7 32 bit + > MySQL 5.5.9 > > > > After creating the databases and granting privileges to the user and > password named in the entityengine.xml file I ran the command: > > > > "ant run-install-seed" from the directory where ofbiz 10.04 OOTB is > installed - This install worked fine with MySQL 5.1. > > > > I get the following error back (actually tons of these errors) > > > > [java] Error was: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: > You have an error in your SQL syntax; check the manual that corresponds to > your MySQL server version for the right syntax to use near 'TYPE InnoDB > CHARACTER SET latin1 COLLATE latin1_general_cs' > > > > > > Has anyone seen this before? > > > > Dead in the water at this point > > > > Thanks > > James > > |
RE: Installing clean new in MySQL 5.5.9
|
|
Thanks - you mean changing these in the entityengine.xml file, right?
The error message below is from this statement CREATE TABLE CARRIER_SHIPMENT_METHOD (SHIPMENT_METHOD_TYPE_ID VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, PARTY_ID VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, ROLE_TYPE_ID VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, SEQUENCE_NUMBER DECIMAL(20,0), CARRIER_SERVICE_CODE VARCHAR(60) CHARACTER SET latin1 COLLATE latin1_general_cs, LAST_UPDATED_STAMP DATETIME, LAST_UPDATED_TX_STAMP DATETIME, CREATED_STAMP DATETIME, CREATED_TX_STAMP DATETIME, CONSTRAINT PK_CARRIER_SHIPMENT_METHOD PRIMARY KEY (SHIPMENT_METHOD_TYPE_ID, PARTY_ID, ROLE_TYPE_ID)) TYPE InnoDB CHARACTER SET latin1 COLLATE latin1_general_cs What's nagging at me is what is the syntax issue with the SQL statement? It was working in another install with MySQL 5.1 and isn't with a new install with MySQL 5.5. THoughts? James -----Original Message----- From: Mike [mailto:[hidden email]] Sent: March-09-11 2:56 PM To: [hidden email] Subject: Re: Installing clean new in MySQL 5.5.9 You probably want to dump the latin1 character set and use UTF8. If you use latin1, you can forget about getting a multi-language capable ofbiz installation (I learned the hard way). Try these: table-type="InnoDB" character-set="utf8" collate="utf8_general_ci"> On Wed, Mar 9, 2011 at 10:58 AM, James Lawton <[hidden email]> wrote: > I have just setup a brand new install on a machine with Windows 7 32 > bit + MySQL 5.5.9 > > > > After creating the databases and granting privileges to the user and > password named in the entityengine.xml file I ran the command: > > > > "ant run-install-seed" from the directory where ofbiz 10.04 OOTB is > installed - This install worked fine with MySQL 5.1. > > > > I get the following error back (actually tons of these errors) > > > > [java] Error was: > You have an error in your SQL syntax; check the manual that > corresponds to your MySQL server version for the right syntax to use > near 'TYPE InnoDB CHARACTER SET latin1 COLLATE latin1_general_cs' > > > > > > Has anyone seen this before? > > > > Dead in the water at this point > > > > Thanks > > James > > |
RE: Installing clean new in MySQL 5.5.9
|
|
In reply to this post by Mike Z
Ahhh...just found a change in the MySQL manuals
==================================== Section 5.1.7, "Server SQL Modes". Note The older TYPE option was synonymous with ENGINE. TYPE was deprecated in MySQL 4.0 and removed in MySQL 5.5. When upgrading to MySQL 5.5 or later, you must convert existing applications that rely on TYPE to use ENGINE instead. ====================================== Does anyone know where I can change the TYPE to ENGINE in the Ofbiz code? James -----Original Message----- From: James Lawton [mailto:[hidden email]] Sent: March-09-11 3:39 PM To: '[hidden email]' Subject: RE: Installing clean new in MySQL 5.5.9 Thanks - you mean changing these in the entityengine.xml file, right? The error message below is from this statement CREATE TABLE CARRIER_SHIPMENT_METHOD (SHIPMENT_METHOD_TYPE_ID VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, PARTY_ID VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, ROLE_TYPE_ID VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, SEQUENCE_NUMBER DECIMAL(20,0), CARRIER_SERVICE_CODE VARCHAR(60) CHARACTER SET latin1 COLLATE latin1_general_cs, LAST_UPDATED_STAMP DATETIME, LAST_UPDATED_TX_STAMP DATETIME, CREATED_STAMP DATETIME, CREATED_TX_STAMP DATETIME, CONSTRAINT PK_CARRIER_SHIPMENT_METHOD PRIMARY KEY (SHIPMENT_METHOD_TYPE_ID, PARTY_ID, ROLE_TYPE_ID)) TYPE InnoDB CHARACTER SET latin1 COLLATE latin1_general_cs What's nagging at me is what is the syntax issue with the SQL statement? It was working in another install with MySQL 5.1 and isn't with a new install with MySQL 5.5. THoughts? James -----Original Message----- From: Mike [mailto:[hidden email]] Sent: March-09-11 2:56 PM To: [hidden email] Subject: Re: Installing clean new in MySQL 5.5.9 You probably want to dump the latin1 character set and use UTF8. If you use latin1, you can forget about getting a multi-language capable ofbiz installation (I learned the hard way). Try these: table-type="InnoDB" character-set="utf8" collate="utf8_general_ci"> On Wed, Mar 9, 2011 at 10:58 AM, James Lawton <[hidden email]> wrote: > I have just setup a brand new install on a machine with Windows 7 32 > bit + MySQL 5.5.9 > > > > After creating the databases and granting privileges to the user and > password named in the entityengine.xml file I ran the command: > > > > "ant run-install-seed" from the directory where ofbiz 10.04 OOTB is > installed - This install worked fine with MySQL 5.1. > > > > I get the following error back (actually tons of these errors) > > > > [java] Error was: > You have an error in your SQL syntax; check the manual that > corresponds to your MySQL server version for the right syntax to use > near 'TYPE InnoDB CHARACTER SET latin1 COLLATE latin1_general_cs' > > > > > > Has anyone seen this before? > > > > Dead in the water at this point > > > > Thanks > > James > > |
|
|
Try upgrading to the latest mysql-connector-java-*.jar and put it in:
OFBIZ_HOME/framework/entity/lib/jdbc On Wed, Mar 9, 2011 at 12:43 PM, James Lawton <[hidden email]> wrote: > Ahhh...just found a change in the MySQL manuals > > ==================================== > > Section 5.1.7, "Server SQL Modes". > > Note > The older TYPE option was synonymous with ENGINE. TYPE was deprecated in > MySQL 4.0 and removed in MySQL 5.5. When upgrading to MySQL 5.5 or later, > you must convert existing applications that rely on TYPE to use ENGINE > instead. > > ====================================== > > > Does anyone know where I can change the TYPE to ENGINE in the Ofbiz code? > > James > > -----Original Message----- > From: James Lawton [mailto:[hidden email]] > Sent: March-09-11 3:39 PM > To: '[hidden email]' > Subject: RE: Installing clean new in MySQL 5.5.9 > > Thanks - you mean changing these in the entityengine.xml file, right? > > The error message below is from this statement > > CREATE TABLE CARRIER_SHIPMENT_METHOD (SHIPMENT_METHOD_TYPE_ID VARCHAR(20) > CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, PARTY_ID > VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, > ROLE_TYPE_ID VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT > NULL, SEQUENCE_NUMBER DECIMAL(20,0), CARRIER_SERVICE_CODE VARCHAR(60) > CHARACTER SET latin1 COLLATE latin1_general_cs, LAST_UPDATED_STAMP DATETIME, > LAST_UPDATED_TX_STAMP DATETIME, CREATED_STAMP DATETIME, CREATED_TX_STAMP > DATETIME, CONSTRAINT PK_CARRIER_SHIPMENT_METHOD PRIMARY KEY > (SHIPMENT_METHOD_TYPE_ID, PARTY_ID, ROLE_TYPE_ID)) TYPE InnoDB CHARACTER SET > latin1 COLLATE latin1_general_cs > > What's nagging at me is what is the syntax issue with the SQL statement? It > was working in another install with MySQL 5.1 and isn't with a new install > with MySQL 5.5. > > THoughts? > > James > > -----Original Message----- > From: Mike [mailto:[hidden email]] > Sent: March-09-11 2:56 PM > To: [hidden email] > Subject: Re: Installing clean new in MySQL 5.5.9 > > You probably want to dump the latin1 character set and use UTF8. If you use > latin1, you can forget about getting a multi-language capable ofbiz > installation (I learned the hard way). Try these: > > table-type="InnoDB" > character-set="utf8" > collate="utf8_general_ci"> > > > On Wed, Mar 9, 2011 at 10:58 AM, James Lawton <[hidden email]> > wrote: >> I have just setup a brand new install on a machine with Windows 7 32 >> bit + MySQL 5.5.9 >> >> >> >> After creating the databases and granting privileges to the user and >> password named in the entityengine.xml file I ran the command: >> >> >> >> "ant run-install-seed" from the directory where ofbiz 10.04 OOTB is >> installed - This install worked fine with MySQL 5.1. >> >> >> >> I get the following error back (actually tons of these errors) >> >> >> >> [java] Error was: > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: >> You have an error in your SQL syntax; check the manual that >> corresponds to your MySQL server version for the right syntax to use >> near 'TYPE InnoDB CHARACTER SET latin1 COLLATE latin1_general_cs' >> >> >> >> >> >> Has anyone seen this before? >> >> >> >> Dead in the water at this point >> >> >> >> Thanks >> >> James >> >> > > > |
RE: Installing clean new in MySQL 5.5.9
|
|
I already have the latest connector installed and in the directory - I have
other machines running Ofbiz 10.04 and using MySQL 5.1 where everything is running... For MySQL 5.5 I think the issue now is that I am going to have to change the SQL creation statements in the code somewhere to no longer use the SQL syntax of "TYPE" and use "ENGINE" instead... Anyone know where in the ofbiz code those statements are pulled together? Thanks James -----Original Message----- From: Mike [mailto:[hidden email]] Sent: March-09-11 3:57 PM To: [hidden email] Subject: Re: Installing clean new in MySQL 5.5.9 Try upgrading to the latest mysql-connector-java-*.jar and put it in: OFBIZ_HOME/framework/entity/lib/jdbc On Wed, Mar 9, 2011 at 12:43 PM, James Lawton <[hidden email]> wrote: > Ahhh...just found a change in the MySQL manuals > > ==================================== > > Section 5.1.7, "Server SQL Modes". > > Note > The older TYPE option was synonymous with ENGINE. TYPE was deprecated > in MySQL 4.0 and removed in MySQL 5.5. When upgrading to MySQL 5.5 or > later, you must convert existing applications that rely on TYPE to use > ENGINE instead. > > ====================================== > > > Does anyone know where I can change the TYPE to ENGINE in the Ofbiz code? > > James > > -----Original Message----- > From: James Lawton [mailto:[hidden email]] > Sent: March-09-11 3:39 PM > To: '[hidden email]' > Subject: RE: Installing clean new in MySQL 5.5.9 > > Thanks - you mean changing these in the entityengine.xml file, right? > > The error message below is from this statement > > CREATE TABLE CARRIER_SHIPMENT_METHOD (SHIPMENT_METHOD_TYPE_ID > VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, > PARTY_ID > VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, > ROLE_TYPE_ID VARCHAR(20) CHARACTER SET latin1 COLLATE > latin1_general_cs NOT NULL, SEQUENCE_NUMBER DECIMAL(20,0), > CARRIER_SERVICE_CODE VARCHAR(60) CHARACTER SET latin1 COLLATE > latin1_general_cs, LAST_UPDATED_STAMP DATETIME, LAST_UPDATED_TX_STAMP > DATETIME, CREATED_STAMP DATETIME, CREATED_TX_STAMP DATETIME, > CONSTRAINT PK_CARRIER_SHIPMENT_METHOD PRIMARY KEY > (SHIPMENT_METHOD_TYPE_ID, PARTY_ID, ROLE_TYPE_ID)) TYPE InnoDB > CHARACTER SET > latin1 COLLATE latin1_general_cs > > What's nagging at me is what is the syntax issue with the SQL > statement? It was working in another install with MySQL 5.1 and isn't > with a new install with MySQL 5.5. > > THoughts? > > James > > -----Original Message----- > From: Mike [mailto:[hidden email]] > Sent: March-09-11 2:56 PM > To: [hidden email] > Subject: Re: Installing clean new in MySQL 5.5.9 > > You probably want to dump the latin1 character set and use UTF8. If > you use latin1, you can forget about getting a multi-language capable > ofbiz installation (I learned the hard way). Try these: > > table-type="InnoDB" > character-set="utf8" > collate="utf8_general_ci"> > > > On Wed, Mar 9, 2011 at 10:58 AM, James Lawton > <[hidden email]> > wrote: >> I have just setup a brand new install on a machine with Windows 7 32 >> bit + MySQL 5.5.9 >> >> >> >> After creating the databases and granting privileges to the user and >> password named in the entityengine.xml file I ran the command: >> >> >> >> "ant run-install-seed" from the directory where ofbiz 10.04 OOTB is >> installed - This install worked fine with MySQL 5.1. >> >> >> >> I get the following error back (actually tons of these errors) >> >> >> >> [java] Error was: > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: >> You have an error in your SQL syntax; check the manual that >> corresponds to your MySQL server version for the right syntax to use >> near 'TYPE InnoDB CHARACTER SET latin1 COLLATE latin1_general_cs' >> >> >> >> >> >> Has anyone seen this before? >> >> >> >> Dead in the water at this point >> >> >> >> Thanks >> >> James >> >> > > > |
Re: Installing clean new in MySQL 5.5.9
|
|
A quick search in the framework will show you the result of where this is. To save you some time, the database meta-data maintenance code is all in the DatabaseUtil.java file. -David On Mar 9, 2011, at 3:15 PM, James Lawton wrote: > I already have the latest connector installed and in the directory - I have > other machines running Ofbiz 10.04 and using MySQL 5.1 where everything is > running... > > For MySQL 5.5 I think the issue now is that I am going to have to change the > SQL creation statements in the code somewhere to no longer use the SQL > syntax of "TYPE" and use "ENGINE" instead... > > Anyone know where in the ofbiz code those statements are pulled together? > > Thanks > James > > -----Original Message----- > From: Mike [mailto:[hidden email]] > Sent: March-09-11 3:57 PM > To: [hidden email] > Subject: Re: Installing clean new in MySQL 5.5.9 > > Try upgrading to the latest mysql-connector-java-*.jar and put it in: > > OFBIZ_HOME/framework/entity/lib/jdbc > > > On Wed, Mar 9, 2011 at 12:43 PM, James Lawton <[hidden email]> > wrote: >> Ahhh...just found a change in the MySQL manuals >> >> ==================================== >> >> Section 5.1.7, "Server SQL Modes". >> >> Note >> The older TYPE option was synonymous with ENGINE. TYPE was deprecated >> in MySQL 4.0 and removed in MySQL 5.5. When upgrading to MySQL 5.5 or >> later, you must convert existing applications that rely on TYPE to use >> ENGINE instead. >> >> ====================================== >> >> >> Does anyone know where I can change the TYPE to ENGINE in the Ofbiz code? >> >> James >> >> -----Original Message----- >> From: James Lawton [mailto:[hidden email]] >> Sent: March-09-11 3:39 PM >> To: '[hidden email]' >> Subject: RE: Installing clean new in MySQL 5.5.9 >> >> Thanks - you mean changing these in the entityengine.xml file, right? >> >> The error message below is from this statement >> >> CREATE TABLE CARRIER_SHIPMENT_METHOD (SHIPMENT_METHOD_TYPE_ID >> VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, >> PARTY_ID >> VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, >> ROLE_TYPE_ID VARCHAR(20) CHARACTER SET latin1 COLLATE >> latin1_general_cs NOT NULL, SEQUENCE_NUMBER DECIMAL(20,0), >> CARRIER_SERVICE_CODE VARCHAR(60) CHARACTER SET latin1 COLLATE >> latin1_general_cs, LAST_UPDATED_STAMP DATETIME, LAST_UPDATED_TX_STAMP >> DATETIME, CREATED_STAMP DATETIME, CREATED_TX_STAMP DATETIME, >> CONSTRAINT PK_CARRIER_SHIPMENT_METHOD PRIMARY KEY >> (SHIPMENT_METHOD_TYPE_ID, PARTY_ID, ROLE_TYPE_ID)) TYPE InnoDB >> CHARACTER SET >> latin1 COLLATE latin1_general_cs >> >> What's nagging at me is what is the syntax issue with the SQL >> statement? It was working in another install with MySQL 5.1 and isn't >> with a new install with MySQL 5.5. >> >> THoughts? >> >> James >> >> -----Original Message----- >> From: Mike [mailto:[hidden email]] >> Sent: March-09-11 2:56 PM >> To: [hidden email] >> Subject: Re: Installing clean new in MySQL 5.5.9 >> >> You probably want to dump the latin1 character set and use UTF8. If >> you use latin1, you can forget about getting a multi-language capable >> ofbiz installation (I learned the hard way). Try these: >> >> table-type="InnoDB" >> character-set="utf8" >> collate="utf8_general_ci"> >> >> >> On Wed, Mar 9, 2011 at 10:58 AM, James Lawton >> <[hidden email]> >> wrote: >>> I have just setup a brand new install on a machine with Windows 7 32 >>> bit + MySQL 5.5.9 >>> >>> >>> >>> After creating the databases and granting privileges to the user and >>> password named in the entityengine.xml file I ran the command: >>> >>> >>> >>> "ant run-install-seed" from the directory where ofbiz 10.04 OOTB is >>> installed - This install worked fine with MySQL 5.1. >>> >>> >>> >>> I get the following error back (actually tons of these errors) >>> >>> >>> >>> [java] Error was: >> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: >>> You have an error in your SQL syntax; check the manual that >>> corresponds to your MySQL server version for the right syntax to use >>> near 'TYPE InnoDB CHARACTER SET latin1 COLLATE latin1_general_cs' >>> >>> >>> >>> >>> >>> Has anyone seen this before? >>> >>> >>> >>> Dead in the water at this point >>> >>> >>> >>> Thanks >>> >>> James >>> >>> >> >> >> > > |
RE: Installing clean new in MySQL 5.5.9
|
|
Got it! Thanks!
Also found a file called Relation.java which has a section involving appending "TYPE" after appending "RELATION" (lines 60, 61, 62) framework\sql\src\org\ofbiz\relation.java Do you know off hand if that one also needs to be changed? I don't think so as it does seem to bear on "CREATE TABLE" Thanks James -----Original Message----- From: David E Jones [mailto:[hidden email]] Sent: March-09-11 5:33 PM To: [hidden email] Subject: Re: Installing clean new in MySQL 5.5.9 A quick search in the framework will show you the result of where this is. To save you some time, the database meta-data maintenance code is all in the DatabaseUtil.java file. -David On Mar 9, 2011, at 3:15 PM, James Lawton wrote: > I already have the latest connector installed and in the directory - I > have other machines running Ofbiz 10.04 and using MySQL 5.1 where > everything is running... > > For MySQL 5.5 I think the issue now is that I am going to have to > change the SQL creation statements in the code somewhere to no longer > use the SQL syntax of "TYPE" and use "ENGINE" instead... > > Anyone know where in the ofbiz code those statements are pulled together? > > Thanks > James > > -----Original Message----- > From: Mike [mailto:[hidden email]] > Sent: March-09-11 3:57 PM > To: [hidden email] > Subject: Re: Installing clean new in MySQL 5.5.9 > > Try upgrading to the latest mysql-connector-java-*.jar and put it in: > > OFBIZ_HOME/framework/entity/lib/jdbc > > > On Wed, Mar 9, 2011 at 12:43 PM, James Lawton > <[hidden email]> > wrote: >> Ahhh...just found a change in the MySQL manuals >> >> ==================================== >> >> Section 5.1.7, "Server SQL Modes". >> >> Note >> The older TYPE option was synonymous with ENGINE. TYPE was deprecated >> in MySQL 4.0 and removed in MySQL 5.5. When upgrading to MySQL 5.5 or >> later, you must convert existing applications that rely on TYPE to >> use ENGINE instead. >> >> ====================================== >> >> >> Does anyone know where I can change the TYPE to ENGINE in the Ofbiz code? >> >> James >> >> -----Original Message----- >> From: James Lawton [mailto:[hidden email]] >> Sent: March-09-11 3:39 PM >> To: '[hidden email]' >> Subject: RE: Installing clean new in MySQL 5.5.9 >> >> Thanks - you mean changing these in the entityengine.xml file, right? >> >> The error message below is from this statement >> >> CREATE TABLE CARRIER_SHIPMENT_METHOD (SHIPMENT_METHOD_TYPE_ID >> VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, >> PARTY_ID >> VARCHAR(20) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, >> ROLE_TYPE_ID VARCHAR(20) CHARACTER SET latin1 COLLATE >> latin1_general_cs NOT NULL, SEQUENCE_NUMBER DECIMAL(20,0), >> CARRIER_SERVICE_CODE VARCHAR(60) CHARACTER SET latin1 COLLATE >> latin1_general_cs, LAST_UPDATED_STAMP DATETIME, LAST_UPDATED_TX_STAMP >> DATETIME, CREATED_STAMP DATETIME, CREATED_TX_STAMP DATETIME, >> CONSTRAINT PK_CARRIER_SHIPMENT_METHOD PRIMARY KEY >> (SHIPMENT_METHOD_TYPE_ID, PARTY_ID, ROLE_TYPE_ID)) TYPE InnoDB >> CHARACTER SET >> latin1 COLLATE latin1_general_cs >> >> What's nagging at me is what is the syntax issue with the SQL >> statement? It was working in another install with MySQL 5.1 and isn't >> with a new install with MySQL 5.5. >> >> THoughts? >> >> James >> >> -----Original Message----- >> From: Mike [mailto:[hidden email]] >> Sent: March-09-11 2:56 PM >> To: [hidden email] >> Subject: Re: Installing clean new in MySQL 5.5.9 >> >> You probably want to dump the latin1 character set and use UTF8. If >> you use latin1, you can forget about getting a multi-language capable >> ofbiz installation (I learned the hard way). Try these: >> >> table-type="InnoDB" >> character-set="utf8" >> collate="utf8_general_ci"> >> >> >> On Wed, Mar 9, 2011 at 10:58 AM, James Lawton >> <[hidden email]> >> wrote: >>> I have just setup a brand new install on a machine with Windows 7 32 >>> bit + MySQL 5.5.9 >>> >>> >>> >>> After creating the databases and granting privileges to the user and >>> password named in the entityengine.xml file I ran the command: >>> >>> >>> >>> "ant run-install-seed" from the directory where ofbiz 10.04 OOTB is >>> installed - This install worked fine with MySQL 5.1. >>> >>> >>> >>> I get the following error back (actually tons of these errors) >>> >>> >>> >>> [java] Error was: >> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: >>> You have an error in your SQL syntax; check the manual that >>> corresponds to your MySQL server version for the right syntax to use >>> near 'TYPE InnoDB CHARACTER SET latin1 COLLATE latin1_general_cs' >>> >>> >>> >>> >>> >>> Has anyone seen this before? >>> >>> >>> >>> Dead in the water at this point >>> >>> >>> >>> Thanks >>> >>> James >>> >>> >> >> >> > > |
Re: Installing clean new in MySQL 5.5.9
|
In reply to this post by Mike Z
Hi all,
The recent discussion at http://ofbiz.135035.n4.nabble.com/data-base-tp3323306p3325260.html seems to suggest the default encoding in OFbiz could now be utf8. Are there any disadvantages, or should we just go and do it? Cheers Paul Foxworthy
--
Coherent Software Australia Pty Ltd http://www.coherentsoftware.com.au/ Bonsai ERP, the all-inclusive ERP system http://www.bonsaierp.com.au/ |
|
|
I bookmarked this article regarding mysql and utf8 a couple of years
ago. It convinced me to always use uft8. http://www.bluetwanger.de/blog/2006/11/20/mysql-and-utf-8-no-more-question-marks/ On Sat, Mar 12, 2011 at 8:56 PM, Paul Foxworthy <[hidden email]> wrote: > Hi all, > > The recent discussion at > http://ofbiz.135035.n4.nabble.com/data-base-tp3323306p3325260.html > http://ofbiz.135035.n4.nabble.com/data-base-tp3323306p3325260.html seems to > suggest the default encoding in OFbiz could now be utf8. > > Are there any disadvantages, or should we just go and do it? > > Cheers > > Paul Foxworthy > > > Mike Z wrote: >> >> You probably want to dump the latin1 character set and use UTF8. If >> you use latin1, you can forget about getting a multi-language capable >> ofbiz installation (I learned the hard way). Try these: >> >> table-type="InnoDB" >> character-set="utf8" >> collate="utf8_general_ci"> >> >> >> On Wed, Mar 9, 2011 at 10:58 AM, James Lawton >> <[hidden email]> wrote: >>> I have just setup a brand new install on a machine with Windows 7 32 bit >>> + >>> MySQL 5.5.9 >>> >>> >>> >>> After creating the databases and granting privileges to the user and >>> password named in the entityengine.xml file I ran the command: >>> >>> >>> >>> "ant run-install-seed" from the directory where ofbiz 10.04 OOTB is >>> installed - This install worked fine with MySQL 5.1. >>> >>> >>> >>> I get the following error back (actually tons of these errors) >>> >>> >>> >>> [java] Error was: >>> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: >>> You have an error in your SQL syntax; check the manual that corresponds >>> to >>> your MySQL server version for the right syntax to use near 'TYPE InnoDB >>> CHARACTER SET latin1 COLLATE latin1_general_cs' >>> >>> >>> >>> >>> >>> Has anyone seen this before? >>> >>> >>> >>> Dead in the water at this point >>> >>> >>> >>> Thanks >>> >>> James >>> >>> >> > > > -- > View this message in context: http://ofbiz.135035.n4.nabble.com/Installing-clean-new-in-MySQL-5-5-9-tp3344284p3351321.html > Sent from the OFBiz - User mailing list archive at Nabble.com. > |
«
Return to OFBiz - User
|
1 view|%1 views
| Free forum by Nabble | Edit this page |