On Sat, 12 Mar 2005 09:25:37 +0100, Dries Buytaert <dries@buytaert.net> wrote:

Difficult to say without proper benchmarking. I'm sure some relations are better captured in separate tables, while for some relations it might be beneficial to use a single table. It all depends on how you want to use (query) the data, and how frequent.

Sounds a bit like a relationship API. Certain modules would define relationships, and depending on the needs/scale, would either use a "shared" relationship table or design their own optimized table.

Personally, I'd start off with extending taxonomy for folksonomies and nothing more.

Yes, please! -- Boris Mann http://www.bryght.com