[Hibernate-JIRA] Commented: (HHH-1829) Allow join on any property using property-ref
by Andrew Seales (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829?page=c... ]
Andrew Seales commented on HHH-1829:
------------------------------------
Maarten,
Thanks for doing the unit tests, that saves me a job I was planning on doing today or tomorrow :)
I'll test them with my patch and see what the results are.
Andrew
> Allow join on any property using property-ref
> ---------------------------------------------
>
> Key: HHH-1829
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829
> Project: Hibernate3
> Type: New Feature
> Components: core
> Versions: 3.2.0 cr1, 3.2.0.cr2
> Reporter: Maarten Winkels
> Assignee: Steve Ebersole
> Fix For: 3.2.2
> Attachments: AbstractJoinTest.java, JoinNoPropertyRefTest.java, JoinPropertyRefTest.java, Person.hbm.xml, Person.java, PersonNoPropertyRef.hbm.xml, hhh-1829.patch
>
>
> Currently joining tables for one class (uing the <join...> tag) is only supported for the id property. The property-ref is allowed on the <key..> tag inside the <join..> tag, but this is ignored.
--
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
19 years, 1 month
[Hibernate-JIRA] Updated: (HHH-1829) Allow join on any property using property-ref
by Maarten Winkels (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829?page=all ]
Maarten Winkels updated HHH-1829:
---------------------------------
Attachment: AbstractJoinTest.java
JoinNoPropertyRefTest.java
JoinPropertyRefTest.java
These are a few unittest that I coded before attempting to solve the problem (exactly the style that you proposed). I never came too solving the problem completely, especially the foreign key property was not generated correctly and the batch updates didn't work.
I didn't check the testcases against the patch, but I do think they show very basic cases where the functionality is needed.
> Allow join on any property using property-ref
> ---------------------------------------------
>
> Key: HHH-1829
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829
> Project: Hibernate3
> Type: New Feature
> Components: core
> Versions: 3.2.0 cr1, 3.2.0.cr2
> Reporter: Maarten Winkels
> Assignee: Steve Ebersole
> Fix For: 3.2.2
> Attachments: AbstractJoinTest.java, JoinNoPropertyRefTest.java, JoinPropertyRefTest.java, Person.hbm.xml, Person.java, PersonNoPropertyRef.hbm.xml, hhh-1829.patch
>
>
> Currently joining tables for one class (uing the <join...> tag) is only supported for the id property. The property-ref is allowed on the <key..> tag inside the <join..> tag, but this is ignored.
--
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
19 years, 1 month
[Hibernate-JIRA] Commented: (HHH-1) Optimize Hibernate for the bulk insertion of related entities
by Martin Ross (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1?page=comm... ]
Martin Ross commented on HHH-1:
-------------------------------
1) seems to hold in case
Class Parent
{
int pk;
}
Class Child
{
int pk;
Parent parent;
}
Class Toy
{
int pk;
Child owner;
}
>From traversing only immediate associations it is easy to see that
Parent.compareTo(Child)==-1 ==> Child.compareTo(Parent) ==1
Toy.compareTo(Child)==1 ==> Child.compareTo(Toy) ==-1
If Parent.compareTo(Child)==-1 and Child.compareTo(Toy)==-1 then we must make sure that Parent.compareTo(Toy)==-1.
It appears the only way to determine if Parent.compareTo(Toy)==-1 is true is to traverse the graph!
> Optimize Hibernate for the bulk insertion of related entities
> -------------------------------------------------------------
>
> Key: HHH-1
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1
> Project: Hibernate3
> Type: New Feature
> Components: core
> Environment: Hibernate 1.2, MySql 3.1
> Reporter: Bradley Leupen
> Priority: Minor
>
>
> It is currently difficult to batch the creation of persistent entities that maintain associations with other entities.
> Add necessary api to hibernate to support the save or update of a collection of entities. An optimization can be applied in this scenario to group inserts / updates by entity class, or table. This will enable the hibernate engine to utilize batching if available, drastically improving performance over a network.
--
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
19 years, 1 month