[Hibernate-JIRA] Resolved: (HBX-623) Add ability in reverse engineering config file to support cascades
by Max Rydahl Andersen (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-623?page=co... ]
Max Rydahl Andersen resolved HBX-623.
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.2.4.CR1)
3.2.4.GA
Ok - I finally managed to get this done.
I did initial work based on your patch (thank you) but quickly realized it was not enough for the full support but I hadn't been able to start without it ;)
I've added a couple of new methods to the Rev.Eng. Strategy:
public AssociationInfo foreignKeyToAssociationInfo(ForeignKey foreignKey);
public AssociationInfo foreignKeyToInverseAssociationInfo(ForeignKey foreignKey);
These returns an AssocationInfo which tells us what value a many-to-one, set or one-to-one or inverse-one-to-one has for cascade, update, insert and fetch.
(I also added foreignKeyToInverseEntityName but that was to fix a side-bug where the naming of one-to-one were not having an effect)
Hope you like it ;)
> Add ability in reverse engineering config file to support cascades
> ------------------------------------------------------------------
>
> Key: HBX-623
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-623
> Project: Hibernate Tools
> Issue Type: Patch
> Components: reverse-engineer
> Affects Versions: 3.0beta2
> Environment: Hibernate Tools Beta 5
> Reporter: tony anecito
> Assignee: Anthony Patricio
> Priority: Critical
> Fix For: 3.2.4.GA
>
> Attachments: many-to-one-attributes-with-test.diff, many-to-one-attributes.diff
>
>
> Please add ability to add cascade tag to resultant mapping files in the reveng file. Currently have to modifiy velocity template file
--
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
17 years, 1 month
[Hibernate-JIRA] Created: (ANN-804) User specified data type for @Version
by Darren Bell (JIRA)
User specified data type for @Version
-------------------------------------
Key: ANN-804
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-804
Project: Hibernate Annotations
Issue Type: Improvement
Affects Versions: 3.4.0.GA
Reporter: Darren Bell
We are creating a database that will be distributed and have multiple masters. This database is being replicated at the database level.
All our id's are guid (32 char hex strings) for this purpose.
The problem we are having that when the same row is updated at two different locations at the same time, they will get the same version number (even if diff columns were updating and the replication engine could handle it).
What we would like is to be able to pass a differene tgenerator to the version annotation and set the type to char(32). Maybe :
@GeneratedValue(generator = "system-uuid")
@GenericGenerator(name = "system-uuid", strategy = "uuid")
This would then work. I know this in javax.persistence, but maybe add a hibernate one as well?
--
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
17 years, 1 month