Debugging table creation

[Kristopher Matthews]

Earlier today one of my tables was failing to be created - no message in any log or output that I could find, just the table wasn't there. So when my unit test attempted to store data in that table, it failed to do so. I eventually (through curse laden trial and error) discovered the culprit:

  @Column(updatable=false)
  protected String foobar;

Commenting out the column annotation fixes the issue. Okay, so maybe that annotation doesn't belong there and is a stupid idea, .. but is there a way to debug this in the future? I'd like to see why the table isn't created, or at least some kind of hint that it wasn't created.

[Kristopher Matthews]

Correction, it has nothing to do with that column annotation. It randomly fails to create the table about 80% of the time. The other 20% it seems to magically work.

INFO: file:/Users/krism/Source/Dentlak/coldfish/build/web/WEB-INF/classes/_ColdFishPu login successful
WARNING: Got SQLException executing statement "CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(15), PRIMARY KEY (SEQ_NAME))": java.sql.SQLException: Table/View 'SEQUENCE' already exists in Schema 'APP'.
WARNING: Got SQLException executing statement "INSERT INTO SEQUENCE(SEQ_NAME, SEQ_COUNT) values ('SEQ_GEN', 0)": java.sql.SQLIntegrityConstraintViolationException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL100930180627120' defined on 'SEQUENCE'.
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.

Notice nothing about my other tables. Or that it is not dropping the sequence table first. Arrrrgh.

[Kristopher Matthews]

Everything is working fine, this was just a litany of errors brought on by a late night and unfamiliarity.

The original problem was that my entity was named "User." The second problem was me not noticing that glassfish was only logging FAILED table create/drops, not successful ones. The third problem was me not refreshing the list of tables in the DB view.