I've been having some odd behavior with database objects getting created for domain objects. Recently I needed to re-create a table with the right constraints, so I changed my dbcreate in DataSource.groovy from "update" to "create-drop" just long enough to rebuild my table.
All was well. I put dbcreate back to "update" and started run-app, and immediately started getting errors on creation of things like the hibernate-sequence. I had seen that before, so I stopped the RunApp and started it up again (yes, this had worked before). Now the table I had recreated is gone, and I have a pile of errors :
Ok, so I put it back to create-drop to see if things could get built, and I continue to get these errors, some on dependencies (foreign key things) and others on simple object creation.Code:2010-08-04 10:36:20,085 [main] ERROR hbm2ddl.SchemaUpdate - Unsuccessful: alter table appquest_applications add id number(19,0) 2010-08-04 10:36:20,085 [main] ERROR hbm2ddl.SchemaUpdate - ORA-00942: table or view does not exist 2010-08-04 10:36:20,085 [main] ERROR hbm2ddl.SchemaUpdate - Unsuccessful: alter table appquest_applications add version number(19,0) 2010-08-04 10:36:20,085 [main] ERROR hbm2ddl.SchemaUpdate - ORA-00942: table or view does not exist and so on for a while...
I can handle blowing everything away and starting over - is that the recommended approach here?
Brian


Reply With Quote