> Sure looks like you're updating positions in a hierarchial collection > of help pages using nested sets, though the algorithm is a touch > different that what I've always used, and I can't say if it's a bug or > if it's just different.
Winner winner, chicken dinner! This query is actually the updating that happens when a page is deleted, maybe that's why the algorithm looks different. > However, I can tell you from experience that > two sequential queries that use the WHERE clause to limit what gets > updated is faster unless the network latency between your app server > and DB server is huge (and so doing one less round trip makes up for > the difference in query execution time). Yeah that's true, it's probably not faster...I guess I just like to bang around in SQL and see what it can do. -- Josh ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:264952 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
