#32 SQL tables should be in lower case

[Anonymous]

the application did not start. in the mysql I noticed few tables are lower case others are in upper case. access_request was created in lower case but the code tries to access it in upper case, and then got the following exception:

Caused by: org.hibernate.HibernateException: Missing table: ACCESS_REQUEST
at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:1086)
at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:116)
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:317)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
... 51 more

tried to rename every thing to the case expected by the application (I used the case from the annotations in the code), but there is a table sequence_list that the app is accessing sometime in lowercases and sometime uppercase. I think it's a good idea to be consistent and use one case and preferably lower case.

[adam]

There is a mismatch between the way the liquibase maven task generated the initial change_set and the way the annotations reference the tables and sequence. Without any changes, express works fine for MySQL & Postgres on OS X and Postgres on Linux. I have not tried other combinations.

I have not stressed too much about this because I am going to update the liquibase change-sets completely in 0.8. I am currently trying to do this and provide 0.7.x users an update path. This is a lot more difficult than you might think.

The current references in code to the sequence_list table all match up. If you need to hack around at the table names you will need to reference the source code to see how the sequence rows see referenced. I am pretty sure this won't be a lot of fun ;-)

Cheers,

Adam