[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-1097?page=c... ] Laurence updated HBX-1097: -------------------------- Attachment: SapDBMetaDataDialect.txt Suggested fix forces null rather than zero length string into the catalog -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-1097?page=c... ] Laurence commented on HBX-1097: ------------------------------- I think the problem arises because in the JDBCReader tables are added to the DatabaseCollector with the catalogName forced to null when a zero length string is found. i.e. if (catalogName!=null && catalogName.trim().length()==0) { catalogName=null; } However when processForeignKeys looks up the foreign key tables it uses the getCatalogForModel() method which leaves a "" zero length string unchanged i.e. fkCatalog = getCatalogForModel((String) exportedKeyRs.get("FKTABLE_CAT")) As a result, all foreign key tables are filtered out because the reference is unknown. I think the same problem would apply if the schema were null. -- 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