HHH-3764, HHH-3765:

documentation

git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@19891 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Adam Warski 2010-07-02 12:57:18 +00:00
parent baba9f5ea8
commit bf9ef75d06
2 changed files with 32 additions and 0 deletions

View File

@ -177,6 +177,32 @@
be the same as the catalog of the normal tables. be the same as the catalog of the normal tables.
</entry> </entry>
</row> </row>
<row>
<entry>
<property>org.hibernate.envers.audit_strategy</property>
</entry>
<entry>
org.hibernate.envers.strategy.DefaultAuditStrategy
</entry>
<entry>
The audit strategy that should be used when persisting audit data. The default stores only the
revision, at which an entity was modified. An alternative,
<literal>org.hibernate.envers.strategy.ValidTimeAuditStrategy</literal> stores additionaly the
end revision, until which the data was valid.
</entry>
</row>
<row>
<entry>
<property>org.hibernate.envers.audit_strategy_valid_time_end_name</property>
</entry>
<entry>
REVEND
</entry>
<entry>
Only valid if the audit strategy is valid-time. Name of the column that will hold the end
revision number in audit entities.
</entry>
</row>
</tbody> </tbody>
</tgroup> </tgroup>
</table> </table>

View File

@ -58,6 +58,12 @@
than corresponding queries on "live" data, as they involve correlated subselects. than corresponding queries on "live" data, as they involve correlated subselects.
</para> </para>
<para>
In the future, queries will be improved both in terms of speed and possibilities, when using the valid-time
audit strategy, that is when storing both start and end revisions for entities. See
<xref linkend="configuration"/>.
</para>
<section id="entities-at-revision"> <section id="entities-at-revision">
<title>Querying for entities of a class at a given revision</title> <title>Querying for entities of a class at a given revision</title>