Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:35 AM
This has been implemented in 2.2 branch.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-203
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-203
Summary: Re-use 1 class over multiple tables w/ same schema
Type: New Feature
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Sam Bravard
Created: Thu, 17 Jul 2003 3:38 AM
Updated: Thu, 11 Dec 2003 12:35 AM
Environment: All
Description:
As far as I can tell, hibernate forces you to apply a single bean against a single table. In comparison to how one normally handles larger multi-table applications in SQL, the one-class to one-table restriction is very limiting.
In many rea-world cases you tend to use multiple tables with identical column layouts (deleted but archived entires, holding queues, etc). Hibernate doesn't appear to support this methodology easily without creating numerous duplicate bean objects that only differ in their 'table' attribute in the .hbm.xml file.
It would be terrific if hibernate could support something along the lines of:
'select cat.name from eg.Cat("tablename") as cat'
so we could easily retarget the table. (the above is just an example - better syntax welcome).
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
