🚀 go-pugleaf

I've just been using the "Change Unidirectional Association to
Bidirectional" on p199 of M. Fowler's Refactoring book.

Since the one-to-many relationship is so fundamental, I would expect much
interest in this refactoring/pattern.

I have however noticed that the example is incomplete: it shows an
addOrder() method but not a removeOrder() method.  Why is that?  Admittedly.
Fowler DOES show the code for a many-to-many relationship where both addXX()
and removeXX() methods are shown - which is elegant and fine by me.

So anyway, turning our attention back to the ONE-to-many (which ends up not
being so elegant, once you flesh it all out - that's my claim...)   I went
ahead and invented/implemented the 'missing' removeOrder() method  thus:

Class Customer ...
 void RemoveCustomer( Order arg ) {
  _orders.remove( arg )
  arg.Customer = nil
}

Notice I had to call
  _orders.remove( arg )
for this to work, which GOES AGAINST the basic idea of the 'controlling'
side of the relationship being the order class, not the customer class (see
his text)

So, with all due respect, is this the reason why fowler didn't show the
implementation of removeCustomer/removeXXX for the one-to-many refactoring
example?  I.e. it would have contradicted his idea of all the 'work' being
done by the controlling side?

-Andy Bulka
WindowWare Multimedia
Australia