Schema Export lacks warning signs --------------------------------- Key: HBX-1161 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1161 Project: Hibernate Tools Issue Type: Improvement Components: eclipse Affects Versions: 3.2.4 Beta1 Environment: Actually, Hibernate Tools 3.3.0.v201002250004M-H277-CR2 Reporter: Joachim Durchholz Priority: Critical In the standard Eclipse install, Hibernate Tools have a list of exporters. One of them is "Schema Export (.ddl)". The standard assumption would be that it's exporting a set of .ddl files (which would have to be manually applied). What actually happens is that any changes are immediately applied to the database. The worst case would be data loss on a production database. (Hey, this just happened to me. Now I'm going to spend the next two hours validating that nothing relevant actually got changed in the DDL.) To avoid unexpected database changes, I propose of the following two changes: 1) Modify the Schema Export exporter to create .ddl files by default. 2) Rename "Schema Export" to "Schema Export (MODIFIES DATABASE BY DEFAULT)", and/or change the icon so it's different from that of "Schema Documentation". (Technically, the two are doing similar things, but the consequences are deeply different.) 3) Split "Schema Export" into "Schema Export" (create .ddl files that can be manually applied) and "Direct Database Schema Update" (apply DDL changes directly to the database). (I'm now off to checking the DDL of the database to see what changes, if any, were applied by Hibernate Tools. Hey, I'm reverse engineering off the production database because the test system is not always up to date.) -- 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