-
Notifications
You must be signed in to change notification settings - Fork 520
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.
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
UOW and cyclic dependencies #1
Comments
@sethstone Hope your well! Apologies for letting this one dangle for so long, i plan a bit of a review of internal and external ideas on the patterns in the coming weeks, so this will get some attention. In the meantime contributors are always welcome! 👍 |
@sethstone Just a quick update to say i'm working on an update to the patterns heading into DF14, this is on the list of supported features. Meanwhile hope all is well with you and the patterns are still serving you well! 👍 |
That sounds great! I'm hoping to attend this year and would like to touch On Mon, Jun 16, 2014 at 7:57 AM, Andrew Fawcett [email protected]
|
Nice, and yes, platform first, code second! |
@adtennant has been working on this recently btw |
See #23 |
@agarciaffdc another that has been merged and can now be closed! 👍 |
Merging apex-common back into personal fork
Feature/test a failing test
The UOW pattern currently doesn't support cyclic dependencies as stated in:
http://andyinthecloud.com/2013/06/09/managing-your-dml-and-transactions-with-a-unit-of-work/
If this could be handled generically in the UOW logic it could be very useful in certain situations. I also agree with Tom Gagne that it may be best to re-factor your data model to avoid this situation altogether, but if it's needed having UOW handle it would be ideal.
The text was updated successfully, but these errors were encountered: