[
https://issues.apache.org/jira/browse/TINKERPOP3-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP3-490.
---------------------------------------
Resolution: Implemented
Fix Version/s: 3.0.0.GA
Assignee: stephen mallette
Technically this was implemented but not for {{GraphStrategy}} as that has been
replaced by {{TraversalStrategy}}. All strategies will be developed within the
context of a {{Traversal}} which simplifies the boilerplate even beyond what
{{GraphStrategy}} did for TP2 "wrapppers". The limitation of course is that
{{TraversalStrategy}} only applies to `Traversal` objects so you can't really
add functionality at the `Graph` level. If someone needs to to do that they
will need to build custom wrappers (which tends to get complicated, at least
insofar as trying to provide a generalized approach to them....maybe easier to
do in a specific domain, but i'm not completely clear on that).
Transaction now has a means to assign callbacks which will fire on
commit/rollback actions. This enables methods to trigger different custom
operations when those things occur (e.g. flush of the queue in
{{EventStrategy}})
> Consider adding transaction hooks to GraphStrategy
> --------------------------------------------------
>
> Key: TINKERPOP3-490
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-490
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: structure
> Reporter: Bryn Cooke
> Assignee: stephen mallette
> Fix For: 3.0.0.GA
>
>
> Being able to detect when a transaction is about to be committed or rolled
> back is useful for recording timestamps on elements.
> It is better to have all of the timestamps recorded within a transaction with
> the same value. Ideally the time just before the transaction is committed
> rather than the time where the element was mutated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
