Hello MySQL Fans First of all, this is not about decision-trees and datamining. And it is not even MySQL-specific.
I would like to use a decision-tree to save our business-rules. Rules are existing and extended frequently. Due to the complexness a hierarchical tree would fit in. (e.g. The Nested Set Model on http://dev.mysql.com/tech-resources/articles/hierarchical-data.html) As I understood a decision-tree there are decision-nodes and leaf-nodes. (http://dms.irb.hr/tutorial/images/dtree_image.gif) Until now, I try to have a "check" and a "set" field in each node, either-way NULL, if it is a decision or a leaf node. But I'm not very happy about it. Does someone have experience to share about the table design and/or queries? Thanks a lot! Jay -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
