Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make TransactionLog aware of changed records #3

Closed
kvesteri opened this issue Jun 12, 2013 · 0 comments
Closed

Make TransactionLog aware of changed records #3

kvesteri opened this issue Jun 12, 2013 · 0 comments

Comments

@kvesteri
Copy link
Owner

We could make something similar to:

http://docs.jboss.org/hibernate/orm/4.2/devguide/en-US/html/ch15.html#envers-tracking-modified-entities-revchanges
@rudaporto rudaporto mentioned this issue Apr 18, 2018
Merged
rudaporto pushed a commit to rudaporto/sqlalchemy-continuum that referenced this issue Apr 18, 2018
track cloned connections
ae0b16e 
Hotfix/track cloned connections (kvesteri#2)

Hotfix/track cloned connections (kvesteri#3)

change iterations

use only ConnectionFairy as indexes

create new dict entry for clones

create entry using old connection

create entry using session

revert to event listening strategy

remove cloned connections on rollback

treat None case when cleaning connections

Hotfix/track cloned connections (kvesteri#2)

Hotfix/track cloned connections (kvesteri#3)

change iterations

use only ConnectionFairy as indexes

create new dict entry for clones

create entry using old connection

create entry using session

revert to event listening strategy

remove cloned connections on rollback

treat None case when cleaning connections
kvesteri pushed a commit that referenced this issue Jun 3, 2018
track cloned connections
acef01b 
Hotfix/track cloned connections (#2)

Hotfix/track cloned connections (#3)

change iterations

use only ConnectionFairy as indexes

create new dict entry for clones

create entry using old connection

create entry using session

revert to event listening strategy

remove cloned connections on rollback

treat None case when cleaning connections

Hotfix/track cloned connections (#2)

Hotfix/track cloned connections (#3)

change iterations

use only ConnectionFairy as indexes

create new dict entry for clones

create entry using old connection

create entry using session

revert to event listening strategy

remove cloned connections on rollback

treat None case when cleaning connections
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kvesteri