Michael Horwitz wrote:
As a rule I would try and avoid circular dependencies wherever possible.
I understand the need to avoid *required* (not null) circular dependencies, but I don't understand why it's not reasonable to have emergent ones. For example, in my app, each user can have a user icon, i.e. a single photo associated with the user. Each piece of media in the system has lots of associated info, for example the user that uploaded it. Clearly this results in a cycle. This causes me grief whenever I have to do a db-load. (My kludge: alter the tables to remove all the foreign key constraints before the db-load, adding those constraints back in afterwards.)
So I recognize that this causes problems, I just don't see why it's not a reasonable schema design, or rather, what other design would still do everything I need and not contain that cycle. Any suggestions?
-Dale --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
