I use it only for display only: Relations such A has-one B, A has-many C, that require additional "stuff" are way beyond this module.
e.g. On delete of A, delete all B, or A has-at-least-one B and so on.
So: only when I have a node-type that we, occasionaly want to expand with some display-stuff. Never when we implement true relations.
Another Rule Of Thumb, is that we should have only very few relations. In cases where each node has one-or-more relations, noderelation cannot scale and we implement our own.
CCK will exist in D7 to provide node references, user references, fieldgroups, field-level permissions, and an upgrade path from the D6 CCK API to the D7 Field API. See http://drupal.org/node/533222 for more information.
There's been talk of splitting up the remaining CCK modules into their own separate projects, but I honestly think that will not happen, especially with the upgrade path being important.
发布评论
评论（2）
我仅将其用于显示：诸如 A 有一个 B、A 有多个 C 之类的需要额外“东西”的关系远远超出了该模块的范围。
例如，删除 A 时，删除所有 B，或者 A 至少有一个 B 等等。
所以：只有当我有一个节点类型时，我们偶尔想要用一些显示内容来扩展。当我们建立真正的关系时永远不会。
另一个经验法则是，我们应该只有很少的关系。在每个节点都有一个或多个关系的情况下，节点关系无法扩展，我们需要实现自己的关系。
I use it only for display only: Relations such A has-one B, A has-many C, that require additional "stuff" are way beyond this module.
e.g. On delete of A, delete all B, or A has-at-least-one B and so on.
So: only when I have a node-type that we, occasionaly want to expand with some display-stuff. Never when we implement true relations.
Another Rule Of Thumb, is that we should have only very few relations. In cases where each node has one-or-more relations, noderelation cannot scale and we implement our own.
CCK 将存在于 D7 中，以提供节点引用、用户引用、字段组、字段级权限以及从 D6 CCK API 到 D7 字段 API 的升级路径。请参阅 http://drupal.org/node/533222 了解更多信息。
有人讨论将剩余的 CCK 模块拆分为自己的单独项目，但老实说，我认为这不会发生，特别是在升级路径很重要的情况下。
CCK will exist in D7 to provide node references, user references, fieldgroups, field-level permissions, and an upgrade path from the D6 CCK API to the D7 Field API. See http://drupal.org/node/533222 for more information.
There's been talk of splitting up the remaining CCK modules into their own separate projects, but I honestly think that will not happen, especially with the upgrade path being important.