Module idea

Inspired by Taxonomy Fields module.

The most amazing thing of Taxonomy Fields is that "content types are not limited to the same range of fields anymore". If it's so why not to go further?

What You think if the availability of some CCK field in some content type will be decided on node level?

Let us suppose, for every field in every content type we can define a php code that returns TRUE (by defaut, field is avaliable, field's data can be added, updated and displayed) or FALSE (the field is not avaliable, an old data is lost).

So we can handle a set of fields for every node dependent on a situation (node taxonomy, for example).

How about a storage costs? For multiple fields we have 1 record per value in separate table so unused fields are gone. For single-value fields we've getting empty cells in content type table for every unused field so it's a trouble.

Unfortunately, 'db_storage' value now is hard-coded with 'multiple' property of the field. I remember how it takes a shape in the throes more than year ago, but I miss how it takes in the current state. I wish somebody tell us about the future of this parameter.

Comments?