[development] relationships API vs i18n

Arnab Nandi arnab at arnab.org
Fri Nov 10 01:13:12 UTC 2006

+1 for relations. I remember sharing some emails with Jeff(eaton)
about this a long time ago; but yes, triples are pretty much the way
to go. So we have:

  CREATE TABLE relation (
    type CHAR(12)
    nid1 int
    nid2 int
    priority int;

which takes care of all possible relations(books, buddylists,
relativity, etc) and has a lightweight ordering mechanism for things
like page numbers, etc.


On 11/9/06, Jeff Eaton <jeff at viapositiva.net> wrote:
> Gabor Hojtsy wrote:
> > By offloading this work to a relationships API, I hope to get more out
> > of this "related nodes" concept then just binary relations of
> > translation nodes. Also this would be something to do for those who are
> > absolutely not interested in i18n, but would like to help bring some
> > cool stuff into Drupal.
> >
> > The existing relations efforts (some ready code) already operate in this
> > field, and category module uses a similar conceptual approach. I hope
> > that this way we can also revitalize the book module.
> That sort of relationship model is (IMO) a necessity for Drupal's
> long-term health. Like everyone else I took a crack at implementing such
> a model and have had it sitting in my sandbox for a few months.
> If we do use 'relationships' as the basis for translation, I hope we
> take the time to do it in such a way that taxonomy terms, buddy lists,
> and other kinds of connections can be represented as well.
> --Jeff


More information about the development mailing list