> for the ongoing effort to develop data-bound Gtk# objects, I have some remark > when it comes to data-binding a TreeView: > When storing a tree data structure in an RDBMS, you would normally define a > table like this: > CREATE TABLE treestore ( > id INTEGER NOT NULL PRIMARY KEY, > super_id INTEGER REFERENCES treestore (id) ON DELETE CASCADE, > name VARCHAR (35) > ); > This means: A line in this table, which has super_id = NULL, represents a > root > node, otherwise it would represent a "branch" (if some other line points at > it with its super_id entry), or a "leaf" (otherwise).
When using a TreeView to display data from an RDBMC I think it is much
more common that the subordinate entries are the result of a foreign key
relation (join or secondary select).
--
Consonance: an Open Source .NET OpenGroupware client.
Contact:[EMAIL PROTECTED] http://freshmeat.net/projects/consonance/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gtk-sharp-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
