[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5560?page=c...
]
Erik-Berndt Scheper commented on HHH-5560:
------------------------------------------
Erik-Berndt Scheper:
{quote}
Indeed: it can be difficult to find a good name for things such as strategies. Names
should be distinctive, short and still describe its intented usage.
Of course, you're right that the start-revision is used by what's now called
'{{ValidAuditTimeStrategy}}', but this is also the case for the
{{DefaultAuditStrategy}}. The use of an end-revision is what sets this strategy apart from
the {{DefaultAuditStrategy}}. And not the fact that it uses a start-revision: that's
what they have in common.
That's why I believe adding 'Start' to the Strategy doesn't add extra
value.
I think that the difference between {{RevisionEndAuditStratigy}} or
{{EndRevisionAudityStrategy}} is arbitrary. Personally I like
{{EndRevisionAudityStrategy}} better.
The reason I originally proposed the name {{RevisionEndColumnAuditStrategy}} (had you
spotted the typo ...) is that this strategy adds the revision-end column (not
end-revision) to the audit tables.
But on second thoughts, I like {{EndRevisionAudityStrategy}} better.
{quote}
Envers ValidAuditTimeStrategy needs a better name
-------------------------------------------------
Key: HHH-5560
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5560
Project: Hibernate Core
Issue Type: Improvement
Components: envers
Affects Versions: 3.6.0.Beta4
Reporter: Erik-Berndt Scheper
Priority: Minor
See:
http://community.jboss.org/thread/156343?tstart=0
I have been thinking about this some time, but I believe we need a better name for the
ValidAuditTimeStrategy.
Of course, this affects both the class name and the envers configuration option.
I think we need to do this ASAP (before 3.6.0 goes CR or even GA), because it will cause
less incompatibility issues.
We could keep the old configuration option for compatibility reasons, but that may not be
necessary since you marked this as experimental.
There are a couple of reasons why I dislike this name
* It suggests that AuditTimes can be invalid. I cannot image how this could be the case.
* We already have AuditStrategy and DefaultAuditStrategy. So it would we logical that the
name should end with AuditStrategy.
* The strategy is based on the use of a revision end column, not on anything like
time(stamp)s.
I propose to rename this strategy to RevisionEndColumnAuditStratigy.
What do you think? If you agree, I could create an issue with a patch to fix this.
--
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