On 2/3/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
the schema creator should still have some say in what kinds of things are allowed/dissalloed though -- the person doing the "update" may not fully understand the underlying model.
I think the two concerns should be separated: 1) updateable docs implementation 2) constraint checking IMO, it's unnecessary to link these features, and requiring (2) will just delay (1). (2) should also cover things unrelated to updateable docs, such as mandatory fields (say someone changes the schema and can't provide a default, and they want the clients to fail until they change). -Yonik