I have a prefix trie. What is the recommended schema for representing this structure in a relational database? I need substring matching to remain efficient.
+1
A:
How about the Materialized Path design?
CREATE TABLE trie (
path VARCHAR(<maxdepth>) PRIMARY KEY,
...other attributes of a tree node...
);
To store a word like "stackoverflow":
INSERT INTO trie (path) VALUES
('s'), ('st'), ('sta'), ('stac'), ('stack'),
('stacko'), ('stackov'), ('stackove'), ('stackover'),
('stackover'), ('stackoverf'), ('stackoverflo'),
('stackoverflow');
The materialized path in the tree is the prefixed sequence of characters itself. This also forms the primary key. The size of the varchar column is the maximum depth of trie you want to store.
I can't think of anything more simple and straightforward than that, and it preserves efficient string storage and searching.
Bill Karwin
2008-12-10 04:15:36
A:
Does any of your entities have a relationship with any other? If not, that is, not relational, a hash table with a serialization would do it.
yogman
2008-12-10 04:30:02
That's really not a trie... I agree that it probably makes sense to keep it out of the db, but turning it into a hashtable?
dgtized
2008-12-10 05:02:14
O(1) algorithms are not good at saving resources. ;)
yogman
2008-12-10 05:16:42