Re: N-to-N Model: Table Size vs Complexity
For performance, you do need a UNION, not OR.
With the 1-row-per-friendship version, you need two indexes. With the 2-rows-per-friendship, you might get away with a single index. This mitigates the cost of doing it that way.
OTOH, the complexity moves to deletions -- you now have to do two deletes.
Subject
Written By
Posted
September 02, 2008 03:18PM
September 03, 2008 08:04AM
September 03, 2008 01:04PM
September 03, 2008 01:29PM
Re: N-to-N Model: Table Size vs Complexity
May 05, 2009 09:37PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.