- Objects ebook, rev 0.4, page 28/29: gets the creator calling DataPortal (Fetch/BeginFetch) <Creator>
- DataAccess ebook, rev 0.5, page 115: gets the creator calling the creator factory method (Creator.GetCreator(), sync/async versions)
The second way looks more "standard", doesn´t it?
For those of us who are learning, having more than way of doing the same is always (at least until we get the whole view) a bit confusing :)
Consistency is good, yes :)
I'll forward this to email@example.com so it gets logged.
You are right, the more consistent approach is to have the child creator implement static factory methods.
After all, the way shown on page 59 Objects, Creator.CreateChild and Creator.FetchChild, seems to bring the benefits of both approaches: compact and clean.
Copyright (c) Marimer LLC