Chris wrote:
>
>On partitioning the graph, it may depend on the underlying technology.
My point exactly. I seek entity design heuristics which minimize the
human intervention required to map into persistence, REGARDLESS OF THE
UNDERLYING TECHNOLOGY. That is, I'm looking for entity persistence
*portability* guidelines, so that I don't have to master designing for
alternate persistence mechanisms. Small, disjoint entities seem the
best *general* pattern for easing persistence mapping.
>With oodb ... isolation on graph updates is not too hard.
But OODB strategies aren't generally applicaple to portable
bean persistence. Entity designs which expect an OODB would
be a pain to persist via O-R mapping. Mind you, I'll be the
first to celebrate when RDBs are irrelevant.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
