[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1825?page=c...
]
Diego Pires Plentz resolved HHH-1825.
-------------------------------------
Assignee: Diego Pires Plentz
Resolution: Cannot Reproduce
Already done.
if ( columnInfo == null ) {
throw new HibernateException( "Missing column: " + col.getName() + " in
" + Table.qualify( tableInfo.getCatalog(), tableInfo.getSchema(),
tableInfo.getName()));
}
Improved mesage in Exception from Table.validateColumns
-------------------------------------------------------
Key: HHH-1825
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1825
Project: Hibernate3
Issue Type: Improvement
Components: metamodel
Affects Versions: 3.1.2
Reporter: Bjørn Bjerkeli
Assignee: Diego Pires Plentz
Priority: Minor
The method validateColumns in Table throws an exception when it encounters a missing
column. Each time I encounter this problem, I have to start the debugger and create a
breakpoint to identify the which table that has the missing column.
So instead of:
if ( columnInfo == null ) {
throw new HibernateException( "Missing column: " + col.getName() );
}
Add proper context to the Exception:
if ( columnInfo == null ) {
throw new HibernateException( "Table:"+this+has " missing column:
" + col.getName() );
}
This will make it trivial to identify and correct the bogus mapping or schema.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira