I really like this change.
"Because the User has a link through the UserAddress it will implicitly add a
hasMany relationship (if not already defined) to the UserAddress. So the
example above is equal to the following:"
hasMany relationship (if not already defined) to the UserAddress. So the
example above is equal to the following:"
I actually created a bug once, because I initially had the relationship from a user to the permission linking table in the reactor.xml, then I changed that to a has many (permission) node with the link name User_PermissionLink.
Well, I had code that referenced the User_PermissionLinkIterator, but it wasn't there anymore!
So, I had to add the hasMany relationship to the Link table back to the xml.
Thank you Doug!
I won't have that error again.
And It'll cut out a lot of unnecessary xml as we move forward.
Chris Phillips
On 4/19/06, Doug Hughes <
[EMAIL PROTECTED]> wrote:
-- Reactor for ColdFusion Mailing List -- [email protected]
-- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
After sleeping on it I came up with a decision on how to fix the delete up
issue.
I've just committed an update which changes the behavior of this to a way
that seems much safer and is, actually, the way it was before (except for
iterators).
