"Unexpected token: AUTO_INCREMENT" or "Wrong data type: BLOB " means
that the parser is not MySQL's, which means that somewhere you're
still using hsqldb instead of mysql, probably, which doesn't know
about auto_increment or blob.
Florent
On 10 Apr 2007, at 11:20, Vincent Dutat wrote:
Hi,
2007-04-10 11:11:05,799 DEBUG
[org.hibernate.tool.hbm2ddl.SchemaUpdate] create table
JBPM_BYTEARRAY (ID_ bigint not null auto_increment, NAME_ varchar
(255), FILEDEFINITION_ bigint, primary key (ID_))
2007-04-10 11:11:05,799 ERROR
[org.hibernate.tool.hbm2ddl.SchemaUpdate] Unsuccessful: create
table JBPM_BYTEARRAY (ID_ bigint not null auto_increment, NAME_
varchar(255), FILEDEFINITION_ bigint, primary key (ID_))
2007-04-10 11:11:05,799 ERROR
[org.hibernate.tool.hbm2ddl.SchemaUpdate] Unexpected token:
AUTO_INCREMENT in statement [create table JBPM_BYTEARRAY (ID_
bigint not null auto_increment]
2007-04-10 11:11:05,799 DEBUG
[org.hibernate.tool.hbm2ddl.SchemaUpdate] create table
JBPM_BYTEBLOCK (PROCESSFILE_ bigint not null, BYTES_ blob, INDEX_
integer not null, primary key (PROCESSFILE_, INDEX_))
2007-04-10 11:11:05,799 ERROR
[org.hibernate.tool.hbm2ddl.SchemaUpdate] Unsuccessful: create
table JBPM_BYTEBLOCK (PROCESSFILE_ bigint not null, BYTES_ blob,
INDEX_ integer not null, primary key (PROCESSFILE_, INDEX_))
2007-04-10 11:11:05,799 ERROR
[org.hibernate.tool.hbm2ddl.SchemaUpdate] Wrong data type: BLOB in
statement [create table JBPM_BYTEBLOCK (PROCESSFILE_ bigint not
null, BYTES_ blob]
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
