We are using Mysql (4.1, Connector-j 5.1.6) as database for archiva
1.0.1 running on JBoss on the same linux box.
On startup, Mysql complains about bad syntax:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: BLOB/TEXT
column 'IDENTIFIER' used in key specification without a key length
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA
ccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons
tructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
at com.mysql.jdbc.Util.getInstance(Util.java:381)
at
com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1030)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1936)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060)
at
com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2536)
at
com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2465)
at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:734)
at
org.jboss.resource.adapter.jdbc.WrappedStatement.execute(WrappedStatemen
t.java:84)
at
org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTab
le.java:614)
at
org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(Abstrac
tTable.java:570)
at
org.jpox.store.rdbms.table.AbstractTable.create(AbstractTable.java:297)
at
org.jpox.store.rdbms.table.AbstractTable.exists(AbstractTable.java:341)
at
org.jpox.store.rdbms.RDBMSManager$ClassAdder.performTablesValidation(RDB
MSManager.java:3065)
at
org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(R
DBMSManager.java:3326)
at
org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2567)
at
org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.j
ava:2419)
at
org.jpox.store.rdbms.RDBMSManager.addClasses(RDBMSManager.java:824)
at
org.jpox.store.rdbms.RDBMSManager.addClass(RDBMSManager.java:838)
at
org.jpox.store.StoreManager.getDatastoreClass(StoreManager.java:1218)
at
org.jpox.store.rdbms.RDBMSManager.getExtent(RDBMSManager.java:1357)
at
org.jpox.AbstractPersistenceManager.getExtent(AbstractPersistenceManager
.java:2328)
at
org.codehaus.plexus.redback.rbac.jdo.JdoTool.getAllObjects(JdoTool.java:
205)
at
org.codehaus.plexus.redback.rbac.jdo.JdoTool.getAllObjects(JdoTool.java:
188)
at
org.codehaus.plexus.redback.rbac.jdo.JdoTool.triggerInit(JdoTool.java:13
1)
at
org.codehaus.plexus.redback.rbac.jdo.JdoTool.getPersistenceManager(JdoTo
ol.java:118)
at
org.codehaus.plexus.redback.rbac.jdo.JdoTool.getObjectById(JdoTool.java:
292)
at
org.codehaus.plexus.redback.rbac.jdo.JdoTool.objectExistsById(JdoTool.ja
va:340)
at
org.codehaus.plexus.redback.rbac.jdo.JdoRbacManager.resourceExists(JdoRb
acManager.java:467)
at
org.codehaus.plexus.redback.rbac.cached.CachedRbacManager.resourceExists
(CachedRbacManager.java:622)
at
org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.pro
cessResources(DefaultRoleModelProcessor.java:77)
at
org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.pro
cess(DefaultRoleModelProcessor.java:63)
at
org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(Defaul
tRoleManager.java:210)
at
org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(Defaul
tRoleManager.java:132)
Does this JDO implementation (jpox) need some dialect configured, like
Hibernate?
