On Feb 1, 2007, at 12:05 AM, Ryan McKinley wrote:
>
> We'd have to make it very clear that this only works if all
fields are
> STORED.
Isn't there some way to do this automatically instead of relying
on documentation? We might need to add something, maybe a
"required" attribute on fields, but a runtime error would be
much, much better than a page on the wiki.
what about copyField?
With copyField, it is reasonable to have fields that are not stored
and are generated from the other stored fields. (this is what my
setup looks like)
I would think copyFields would be exempt from the STORED mandate, and
only the <field> definitions would matter for an update restriction.
Erik
