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

add support for System class>>enableSignaledFinishTransactionError #13

Open
dalehenrich opened this issue Dec 30, 2014 · 0 comments
Open

add support for System class>>enableSignaledFinishTransactionError #13

dalehenrich opened this issue Dec 30, 2014 · 0 comments
Milestone
1.0.10

Comments

@dalehenrich
Copy link
Member

The initial implementation is based on running the gem server in manual transaction mode. However, if we support System class>>enableSignaledFinishTransactionError, a gem server can run in automatic transaction mode ...

Automatic transaction mode has one drawback in that is possible to commit unintended changes to persistent objects, as you will get an ImproperOperation signalled if you attempt to commit without first doing a beginTransaction...

Nonetheless, there is no reason to not support automatic transaction mode.....
@dalehenrich dalehenrich modified the milestones: 1.0.2, 1.0.3, 1.0.4 Jan 9, 2015
@dalehenrich dalehenrich modified the milestones: 1.0.4, 1.0.5, 1.0.6, 1.0.7 Jan 26, 2015
@dalehenrich dalehenrich modified the milestones: 1.0.7, 2.0.1 May 28, 2015
@dalehenrich dalehenrich modified the milestones: 1.0.9, 1.0.10 Jul 15, 2015
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
1.0.10
Development

No branches or pull requests
1 participant
@dalehenrich