Since I want to understand all the modules I use, I also want to understand nodefamily. I mainly want to know why this module is needed for the implementation of the "users as nodes" concept.

Nodefamily provides a relationship functionality. There's a parent content-type, and a child content-type, and there's a DB table that stores this relationship.

But why is this DB table necessary, and this API, when a simple SQL query can show this relationship? That's the Big Question that I just don't get. Why 1,000 lines of code for something so simple that one SQL query can do?

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Fixed

nodefamily allows one to build nodeprofiles, which exist of more than one content type.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.