- support for indexed "fake" bidirectional relations
- adding a field-calculation-phase, after all metadata is read from annotations, but before any audit entities generation is done
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18236 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- if a field is non-insertable in a "fake" bidirectional relation, not storing modifications made on the non-insertable side
- also, not generating bidirectional collection changes in such case
- updating test
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18226 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- adding support for multiple "fake" bidirectional relations
- downgrading testng back to 5.8 as using 5.10 was OOMing the tests
- updating h2 dependency to a newer version
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18225 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- adding support for "fake" bidirectional many-to-one relations using an experimental @AuditMappedBy annotation
- adding a new work unit, extracting common work unit code
- upgrading TestNG to 5.10
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18224 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- changing the way work unit collision is resolved: now work units are merged, the result is a work unit (possibly new)
- work units should behave as immutable objects
- test
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18208 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- fix for removing an item from a persistent collection, flushing, and adding the same item again: merging the collection change work units data
- test
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18163 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- renaming properties from camel case to use _ to separate words, as is the Hibernate convention
- old property names are still supported
- updating documentation
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18152 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- when using join-inheritance, the columns in child entities which map to the revision number use the correct sql-type
- test
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18150 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- adding a register of all audit entity names generated so far
- generating a unique entity name in case of a relation owned by both sides
- fixing the test
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18118 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- handling the case when the revision number in the revision entity uses a @Column(columnDefinition=): the sql-type is property is then set on the REV property of audit entities
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18068 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- applying patch from Nicolas Rougé
- the revision timestamp can now be a j.u.Date or a j.s.Date, and be mapped to a Date in the DB
- test
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@18032 1b8cb986-b30d-0410-93ca-fae66ebed9b2
- adding an option to store the data when an entity is deleted in the revision (instead of having to read the last-but-one revision)
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@16981 1b8cb986-b30d-0410-93ca-fae66ebed9b2