Possible better way to do thread hierarchies

Post #1,165 by drewk 7/9/01 11:41:49 AM Reply	Possible better way to do thread hierarchies Can't remember where the links for this came up, but it suggests a different way of representing message threading. Seems odd at first, but the idea is that inserts, deletes and re-parenting are comparatively rare events most of the time compared to selects. This method optomizes the structure for easier selects, at the expense of some compute time to do an insert. [link\|http://www.dbmsmag.com/9603d06.html\|http://www.dbmsmag.com/9603d06.html] [link\|http://www.intelligententerprise.com/001020/celko1_1.shtml\|http://www.intellig...lko1_1.shtml] This is my sig. There are many like it, but this one is mine.
Post #1,166 by admin 7/9/01 11:50:53 AM Reply	Muah. Have you looked at the [link\|/forums/SourceCode\|SQL code] yet? :-) I've been advocating nested set trees for hierarchical data for a long time. For forums specifically, too, since they are read-mostly. :-) Regards, -scott anderson
Post #1,167 by dpeterson 7/9/01 12:01:04 PM Reply	Other article [link\|http://www.dbmsmag.com/9809d05.html\|http://www.dbmsmag.com/9809d05.html] I've found that the helper table (in figure 3) is a better solution for traversing trees from an aritrary starting point when you have a system in which the tree is changing often. It's a trade off between space and speed. The table can take up quite a bit of space, but it's relatively easy and quick to update and it's fast to query against. Darryl A. Peterson I'm not as funny as I think I am.

Welcome to IWETHEY!