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.

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

Closed
sethstone opened this issue Dec 2, 2013 · 7 comments
Closed

UOW and cyclic dependencies #1

sethstone opened this issue Dec 2, 2013 · 7 comments

Comments

@sethstone
Copy link

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/

Note: If you have some cyclic dependencies in your schema, you will have to either use two separate unit of work instances or simply handle this directly using DML.

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.

@afawcett
Copy link
Contributor

afawcett commented Apr 9, 2014

@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! 👍

@afawcett
Copy link
Contributor

@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! 👍

@sethstone
Copy link
Author

That sounds great! I'm hoping to attend this year and would like to touch
base. So far the patterns are holding up; although we're picking and
choosing more carefully what gets implemented as custom Apex.

On Mon, Jun 16, 2014 at 7:57 AM, Andrew Fawcett notifications@github.com
wrote:

@sethstone https://github.com/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! [image: 👍]


Reply to this email directly or view it on GitHub
#1 (comment)
.

@afawcett
Copy link
Contributor

Nice, and yes, platform first, code second!

@afawcett
Copy link
Contributor

afawcett commented Oct 2, 2014

@adtennant has been working on this recently btw

@afawcett
Copy link
Contributor

afawcett commented Oct 2, 2014

See #23

afawcett pushed a commit that referenced this issue May 21, 2015
afawcett pushed a commit that referenced this issue May 23, 2015
afawcett pushed a commit that referenced this issue Aug 12, 2017
agarciaffdc pushed a commit that referenced this issue Jan 29, 2019
)

Use mock, send-email class which verifies DoWork method was called.  We should presume the platform's Messaging feature functions, as used in the default SendEmailWork class.
agarciaffdc pushed a commit that referenced this issue Jan 29, 2019
agarciaffdc pushed a commit that referenced this issue Jan 29, 2019
@afawcett
Copy link
Contributor

@agarciaffdc another that has been merged and can now be closed! 👍

ImJohnMDaniel pushed a commit that referenced this issue Jan 17, 2022
Merging apex-common back into personal fork
rob-baillie-ortoo referenced this issue in OrtooApps/fflib-apex-common May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants