Title:
Bug 83474:When using Hibernate to create the database tables (via dropcreate=true}, the generated tables have the columns in no predictable order if the entity extends a mappedSuperclass
| View in TrackerStatus/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): marc esher / marc esher (marcesher)
Created: 07/01/2010
Components: ORM Support
Versions: 9.0.1
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 / 276120
Priority/Frequency: Minor / Unknown
Locale/System: English / Platforms All
Vote Count: 0
Problem:
When using Hibernate to create the database tables (via dropcreate=true}, the generated tables have the columns in no predictable order if the entity extends a mappedSuperclass. While this doesn't affect the application, per se, it does lead to hard-to-understand tables and requires extra work to get appropriate resultsets when running queries directly in the client GUI (sql server mgmt studio, for example).When not extending a mappedSuperclass, column ordering works as expected, i.e. columns are ordered in the same manner as the properties are defined in the component
Method:
1. Create a CFC that is a mapped superclass. Give it some properties2. Create a CFC that extends the mapped superclass entity. Give it some properties3. Use Hibernate to create the tables via ormsettings.dropcreate=true4. Inspect the table in the client gui. The column order will not match the order of the properties as defined in the CFC
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3041728
External Customer Info:
External Company:
External Customer Name: marc esher
External Customer Email: 70390EBF47F01CAF992015B9
External Test Config: 07/01/2010Attachments:
Comments: