SchemaUpdate asks for all referenced mapping documents when updating a single table ----------------------------------------------------------------------------------- Key: HHH-2638 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2638 Project: Hibernate3 Issue Type: Improvement Affects Versions: 3.2.0 cr1 Environment: myql, Reporter: bhomass I believe the idea of doing schema update is so that you can update a single table with a single property. However, as I try this feature out, hibernate continues to throw exception because this table I want to update refers to an unmapped class. I can move to the next step by adding another map file, but then more and more unmapped classes get involved, and pretty soon, I am feeding the entire collection of map files. So that's no different from updating the entire database. I think it should be possible automatically read out the existing schema of the referenced tables from the database, so that their mapping files don't need to be supplied to SchemaUpdate, and these referenced tables do not inadvertently get updated too (with no net effect of course). -- 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