On 21 Jun 2011, at 11:15 PM, Thomas Fox wrote:
These two approaches also have problems
- they also bloat a class API which is already big
- If one table has several foreign keys, user could want some
relations to
be filled and some not. This can not be achieved with the above
approach.
This affects us, we are in a situation where we want certain relations
to be filled and others to be left alone on a case by case basis.
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
