On Mon, Mar 29, 2004 at 11:44:49AM -0500, Alan Weissman wrote:
> So for your specific problem, I would go with #1 and put a department
> object on an Employee. If you give me more information on what your
> schema and use cases are, I can help you with the persistence layer.
Well, I was just proposing the question in general and using
Employee/Department as an example. I guess as a compromise
approach, I'd nest Department in Employee and for a
"getEmployees" query I simply wouldn't populate everything
that a Department could possibly contain. This approach
creates some awkwardness though since now you'd also need a
specialized "department query" that would only pertain to
when you are getting back a List of employees, otherwise the
common approach seems to be just populate everything in
Department and jam into each Employee object. (A lot of
extra overhead imo for say all you might want is
departmentName out of the object).
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
