Thanks for the quick answer.
No, i dont use the cvs builds.
I found the log4j.property file deep down in jar archives but with all loggers set to debug.
I decided to start eclipse from the console to have the log statements seen on stdout.
If I execute the statements as to be found in the debug-log manually on the db they don't generate a warning or an error.
here are the statements to my tabel ANLAGE (but the error occures to all tables that are generated):
15:57:09,060 DEBUG SessionFactoryObjectFactory:76 - registered: 4028808706c6340b0106c63897440001 (unnamed)
15:57:09,060 INFO SessionFactoryObjectFactory:82 - Not binding factory to JNDI, no JNDI name configured
15:57:09,061 DEBUG SessionFactoryImpl:297 - instantiated session factory
15:57:09,061 INFO SessionFactoryImpl:429 - Checking 0 named queries
15:57:11,561 INFO Dialect:100 - Using dialect: org.hibernate.dialect.MySQLInnoDBDialect
15:57:11,563 INFO Configuration:995 - processing extends queue
15:57:11,565 INFO Configuration:999 - processing collection mappings
15:57:11,566 INFO Configuration:1008 - processing association property references
15:57:11,568 INFO Configuration:1030 - processing foreign key constraints
15:57:11,624 DEBUG Configuration:1081 - resolving reference to class: beans.Anlage
15:57:11,880 INFO SchemaExport:153 - Running hbm2ddl schema export
15:57:11,882 INFO SchemaExport:175 - exporting generated schema to database
15:57:11,883 INFO DriverManagerConnectionProvider:41 - Using Hibernate built-in connection pool (not for production use!)
15:57:11,885 INFO DriverManagerConnectionProvider:42 - Hibernate connection pool size: 20
15:57:11,886 INFO DriverManagerConnectionProvider:45 - autocommit mode: false
15:57:11,888 INFO DriverManagerConnectionProvider:80 - using driver: com.mysql.jdbc.Driver at URL: jdbc:mysql://localhost:3306/planets
15:57:11,919 DEBUG SchemaExport:278 - alter table ANLAGE drop foreign key FK7359B2C05E899101
15:57:11,920 DEBUG SchemaExport:267 - Unsuccessful: alter table ANLAGE drop foreign key FK7359B2C05E899101
15:57:11,920 DEBUG SchemaExport:268 - Table 'planets.ANLAGE' doesn't exist
15:57:11,921 DEBUG SchemaExport:278 - alter table ANLAGE drop foreign key FK7359B2C09DD8B0C5
15:57:11,921 DEBUG SchemaExport:267 - Unsuccessful: alter table ANLAGE drop foreign key FK7359B2C09DD8B0C5
15:57:11,922 DEBUG SchemaExport:268 - Table 'planets.ANLAGE' doesn't exist
15:57:12,078 DEBUG SchemaExport:278 - drop table if exists ANLAGE
15:57:12,249 DEBUG SchemaExport:278 - create table ANLAGE (ANLAGEN_ID int UNSIGNED not null auto_increment, VERSION integer not null, STUFE smallint UNSIGNED not null, ANLAGENTYP_ID varchar(255), GEBAEUDE_ID varchar(255), primary key (ANLAGEN_ID)) type=InnoDB
15:57:15,620 DEBUG SchemaExport:278 - alter table ANLAGE add index FK7359B2C05E899101 (GEBAEUDE_ID), add constraint FK7359B2C05E899101 foreign key (GEBAEUDE_ID) references PRODUKTIONSGEBAEUDE (GEBAEUDE_ID)
15:57:15,760 DEBUG SchemaExport:278 - alter table ANLAGE add index FK7359B2C09DD8B0C5 (ANLAGENTYP_ID), add constraint FK7359B2C09DD8B0C5 foreign key (ANLAGENTYP_ID) references ANLAGENTYP (ANLAGENTYP_ID)
15:57:15,847 ERROR SchemaExport:253 - Unsuccessful: alter table ANLAGE add index FK7359B2C09DD8B0C5 (ANLAGENTYP_ID), add constraint FK7359B2C09DD8B0C5 foreign key (ANLAGENTYP_ID) references ANLAGENTYP (ANLAGENTYP_ID)
15:57:15,848 ERROR SchemaExport:254 - Can't create table './planets/#sql-152e_c.frm' (errno: 150)
15:57:25,553 INFO SchemaExport:195 - schema export complete
15:57:25,554 DEBUG DriverManagerConnectionProvider:129 - returning connection to pool, pool size: 1
15:57:25,556 INFO DriverManagerConnectionProvider:147 - cleaning up connection pool: jdbc:mysql://localhost:3306/planets
|