Rob Rohan wrote: > It seems though, if you are need that much nested data there is probably a > better solution to the problem then this type of tree model (i.e. using > master - detail tables) that a database might be more optimized for (or > perhaps xml might be a solution).
Databases indeed are not particularly well suited for this type of data, but it is not like they will choke once you reach the 100 records. There are basically 3 models, nested sets, adjacency tree and a path method. Which one is best suited for you depends on many things, such as size of the dataset, (relative) insert/update/delete/select frequency and even the used database (DB2 has a rather complete implementation of WITH which helps with adjacency lists, and Oracle has CONNECT for that). But if you wish to store really large trees, I would recommend consulting somebody who knows your database platform in dept, because database internals such as table locking strategies and index concurrency will kill your performance if you choose the wrong one. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
