I am proposing removing body, title, revisions, and anything like that from the base object of node. Those get added specifically to what is now node.<br><br>I also agree with the fact that users can't/won't be nodes, but I think profiles should. However, that would require nodes (profiles) to be bound users - this could be viewed as good or bad, depending on how you look at it.
<br><br>Dmitri<br><br><div class="gmail_quote">On Dec 29, 2007 1:29 PM, Karoly Negyesi <<a href="mailto:karoly@negyesi.net">karoly@negyesi.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
a) field API is coming. once CCK D6 is out, we will examine the situation.<br><br>b) There is already talk and code how to add relationships to schema API thus making node loads (mostly) one query. Some are considering on-demand loading.
<br><br>c) Also there is talk and code on how registry module hooks. This will also bring some benefits.<br><br>d) I plan on working on code to load multiple load at once.<br><br>Removing body & friends buys us nothing. Turning into user nodes - nay. User profiles -- maybe. Comments -- yes.
<br><br>Regards,<br><br>NK<br></blockquote></div><br>