Thread: [Hibernate-issues] [Hibernate-JIRA] Commented: (HB-152) Ability to map one class across two or more

An object relational-mapping (ORM) library for Java

Brought to you by: davidedalto, dreab8, epbernard, gsmet, and 5 others

hibernate-issues

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-152) Ability to map one class across two or more tables

From: <leg...@at...> - 2003-12-08 02:25:41

The following comment has been added to this issue:

     Author: GoldenYears
    Created: Sun, 7 Dec 2003 8:25 PM
       Body:
For this function.
An mapping class is used for dynamaic filed and property map.
An collection is used for one-to-many list.
An indentify is used for one class to multi table mapping.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-152


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-152
    Summary: Ability to map one class across two or more tables
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:33 PM
    Updated: Sun, 7 Dec 2003 8:25 PM

Description:
Assumption is that
the tables can all be joined with regular joins all the time, and that the key structure
matches, although the name of the columns may differ across the tables.  An insert of an
object results in an insert to each of the mapped tables all using the same key value.  The
class can then map its properties to any column in any table.  This should all be done
without the workaround of using a delegate.  Thank you.


---------------------------------------------------------------------
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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-152) Ability to map one class across two or more tables

From: <leg...@at...> - 2004-03-08 08:11:59

The following comment has been added to this issue:

     Author: CVS Notification Service
    Created: Mon, 8 Mar 2004 1:53 AM
       Body:
CVS COMMIT LOG: 
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/cfg Binder.java,1.26.2.46.2.14,1.26.2.46.2.15
support for a single <join> element in EntityPersister TODO-33 HB-152


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-152


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-152
    Summary: Ability to map one class across two or more tables
       Type: New Feature

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.2 alpha
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:33 PM
    Updated: Mon, 8 Mar 2004 1:53 AM

Description:
Assumption is that
the tables can all be joined with regular joins all the time, and that the key structure
matches, although the name of the columns may differ across the tables.  An insert of an
object results in an insert to each of the mapped tables all using the same key value.  The
class can then map its properties to any column in any table.  This should all be done
without the workaround of using a delegate.  Thank you.


---------------------------------------------------------------------
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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-152) Ability to map one class across two or more tables

From: <leg...@at...> - 2004-03-08 08:11:59

The following comment has been added to this issue:

     Author: CVS Notification Service
    Created: Mon, 8 Mar 2004 1:53 AM
       Body:
CVS COMMIT LOG: 
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/mapping PersistentClass.java,1.14.2.19.2.5,1.14.2.19.2.6 RootClass.java,1.13.2.3.2.1,1.13.2.3.2.2 Subclass.java,1.10.2.3.2.4,1.10.2.3.2.5
support for a single <join> element in EntityPersister TODO-33 HB-152


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-152


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-152
    Summary: Ability to map one class across two or more tables
       Type: New Feature

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.2 alpha
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:33 PM
    Updated: Mon, 8 Mar 2004 1:53 AM

Description:
Assumption is that
the tables can all be joined with regular joins all the time, and that the key structure
matches, although the name of the columns may differ across the tables.  An insert of an
object results in an insert to each of the mapped tables all using the same key value.  The
class can then map its properties to any column in any table.  This should all be done
without the workaround of using a delegate.  Thank you.


---------------------------------------------------------------------
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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-152) Ability to map one class across two or more tables

From: <leg...@at...> - 2004-03-08 08:11:59

The following comment has been added to this issue:

     Author: CVS Notification Service
    Created: Mon, 8 Mar 2004 1:53 AM
       Body:
CVS COMMIT LOG: 
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/proxy LazyInitializer.java,1.10.2.4.2.3,1.10.2.4.2.4
support for a single <join> element in EntityPersister TODO-33 HB-152


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-152


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-152
    Summary: Ability to map one class across two or more tables
       Type: New Feature

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.2 alpha
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:33 PM
    Updated: Mon, 8 Mar 2004 1:53 AM

Description:
Assumption is that
the tables can all be joined with regular joins all the time, and that the key structure
matches, although the name of the columns may differ across the tables.  An insert of an
object results in an insert to each of the mapped tables all using the same key value.  The
class can then map its properties to any column in any table.  This should all be done
without the workaround of using a delegate.  Thank you.


---------------------------------------------------------------------
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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-152) Ability to map one class across two or more tables

From: <leg...@at...> - 2004-03-08 08:12:00

The following comment has been added to this issue:

     Author: CVS Notification Service
    Created: Mon, 8 Mar 2004 1:53 AM
       Body:
CVS COMMIT LOG: 
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/util ArrayHelper.java,1.6.2.3.2.1,1.6.2.3.2.2
support for a single <join> element in EntityPersister TODO-33 HB-152


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-152


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-152
    Summary: Ability to map one class across two or more tables
       Type: New Feature

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.2 alpha
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:33 PM
    Updated: Mon, 8 Mar 2004 1:53 AM

Description:
Assumption is that
the tables can all be joined with regular joins all the time, and that the key structure
matches, although the name of the columns may differ across the tables.  An insert of an
object results in an insert to each of the mapped tables all using the same key value.  The
class can then map its properties to any column in any table.  This should all be done
without the workaround of using a delegate.  Thank you.


---------------------------------------------------------------------
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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-152) Ability to map one class across two or more tables

From: <leg...@at...> - 2004-03-08 08:12:00

The following comment has been added to this issue:

     Author: CVS Notification Service
    Created: Mon, 8 Mar 2004 1:53 AM
       Body:
CVS COMMIT LOG: 
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate hibernate-mapping-2.0.dtd,1.34.2.27.2.5,1.34.2.27.2.6
support for a single <join> element in EntityPersister TODO-33 HB-152


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-152


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-152
    Summary: Ability to map one class across two or more tables
       Type: New Feature

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.2 alpha
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:33 PM
    Updated: Mon, 8 Mar 2004 1:53 AM

Description:
Assumption is that
the tables can all be joined with regular joins all the time, and that the key structure
matches, although the name of the columns may differ across the tables.  An insert of an
object results in an insert to each of the mapped tables all using the same key value.  The
class can then map its properties to any column in any table.  This should all be done
without the workaround of using a delegate.  Thank you.


---------------------------------------------------------------------
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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-152) Ability to map one class across two or more tables

From: <leg...@at...> - 2004-03-08 08:12:01

The following comment has been added to this issue:

     Author: CVS Notification Service
    Created: Mon, 8 Mar 2004 1:53 AM
       Body:
CVS COMMIT LOG: 
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/persister AbstractEntityPersister.java,1.33.2.59.2.8,1.33.2.59.2.9 EntityPersister.java,1.38.2.34.2.6,1.38.2.34.2.7 NormalizedEntityPersister.java,1.32.2.37.2.8,1.32.2.37.2.9
support for a single <join> element in EntityPersister TODO-33 HB-152


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-152


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-152
    Summary: Ability to map one class across two or more tables
       Type: New Feature

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.2 alpha
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:33 PM
    Updated: Mon, 8 Mar 2004 1:53 AM

Description:
Assumption is that
the tables can all be joined with regular joins all the time, and that the key structure
matches, although the name of the columns may differ across the tables.  An insert of an
object results in an insert to each of the mapped tables all using the same key value.  The
class can then map its properties to any column in any table.  This should all be done
without the workaround of using a delegate.  Thank you.


---------------------------------------------------------------------
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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-152) Ability to map one class across two or more tables

From: <leg...@at...> - 2004-03-08 08:22:59

The following comment has been added to this issue:

     Author: CVS Notification Service
    Created: Mon, 8 Mar 2004 2:04 AM
       Body:
CVS COMMIT LOG: 
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/mapping Join.java,NONE,1.1.2.1
support for a single <join> element in EntityPersister TODO-33 HB-152


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-152


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-152
    Summary: Ability to map one class across two or more tables
       Type: New Feature

     Status: Closed
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.2 alpha
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:33 PM
    Updated: Mon, 8 Mar 2004 2:04 AM

Description:
Assumption is that
the tables can all be joined with regular joins all the time, and that the key structure
matches, although the name of the columns may differ across the tables.  An insert of an
object results in an insert to each of the mapped tables all using the same key value.  The
class can then map its properties to any column in any table.  This should all be done
without the workaround of using a delegate.  Thank you.


---------------------------------------------------------------------
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