Hi Tammo, Ah, good point. I didn't even notice the version number in the schema filename. Odd that it seemed to fix a problem I was having running Beta 3 to an external MySQL database however?
So anyway, I assume these generated schemas you are referring (in the case of hibernate for example) are the ones I see in the resulting dao-hibernate-db\target directory after I build - correct? Or is this the hibernate schema for the JBI implementation? For the record, I am attempting to run the axis2-war version of ODE against an external database (MySQL for starters, but ideally DB2). I had been running a Beta 3 build most recently to see if it runs any cleaner, but it sounds like maybe I should stick to Beta 2 for now (until Beta 3 is released)? Thanks David McLure Tammo van Lessen wrote: > > David, > > david_mclure wrote: >> I am finding that the initial problem I mentioned anyway, was due to the >> following missing schema item: Integer EXEC_STATE_COUNTER in the posted >> sql >> file on the ODE web site: >> http://ode.apache.org/war-deployment.data/ode_openjpa_mysql-1.3.2.sql. >> >> Could it be that the schema which is checked into the >> trunk on the Carbon subversion repository is actually the correct schema >> to >> be using for ODE 2 Beta 3, and it simply has yet to be published on the >> ODE >> web page? > > As indicated by the filename, the schema you were referring to is for > ODE 1.3.2. The version in the WSO2 repository is probably better for ODE > 2.0. However, since ODE 2 beta 3 is not yet released, I suggest to build > ODE and take the generated schemas. > > HTH, > Tammo > > -- > Tammo van Lessen - http://www.taval.de > > -- View this message in context: http://old.nabble.com/SQL-Exception-attempting-to-substitute-MySQL-for-Derby-on-ODE-tp27772399p28029464.html Sent from the Apache Ode User mailing list archive at Nabble.com.
