I am using the modified preorder tree traversal algorhythm to maintain downlines and uplines. The effiency is great, allowing me to traverse the uplines and downlines in one query wherever they're needed throughout the application.
I'm worried about once this application starts getting a decent amount of members. When new members are inserted into downlines, the left and right boundaries of a good portion of the downline table will have to be reindexed on every insert. How can I maximize efficiency of this? Is it worthy of NOT indexing those table fields and risk slower queries throughout the application?
downline efficiency
Moderator: General Moderators
downline efficiency
Set Search Time - A google chrome extension. When you search only results from the past year (or set time period) are displayed. Helps tremendously when using new technologies to avoid outdated results.
If the downline is dynamic (via referrals), then the downline tree is updated in different spots throughout the entire table depending on the referrer. It's not a single downline/upline.
Set Search Time - A google chrome extension. When you search only results from the past year (or set time period) are displayed. Helps tremendously when using new technologies to avoid outdated results.
Oh, nevermind, I see what you're saying. I wonder if that's a good tactic or not.
Set Search Time - A google chrome extension. When you search only results from the past year (or set time period) are displayed. Helps tremendously when using new technologies to avoid outdated results.
- Kieran Huggins
- DevNet Master
- Posts: 3635
- Joined: Wed Dec 06, 2006 4:14 pm
- Location: Toronto, Canada
- Contact: