On Mon, Sep 20, 2010 at 12:34 AM, Randall Leeds wrote:
> On Thu, Sep 9, 2010 at 12:19, James Jackson wrote:
>> Hi all,
>>
>> Moving this from the users forum, as it appears what I'm after isn't
>> currently available. For the security model I with to implement in a
>> production CouchDB cluster
On Thu, Sep 9, 2010 at 12:19, James Jackson wrote:
> Hi all,
>
> Moving this from the users forum, as it appears what I'm after isn't
> currently available. For the security model I with to implement in a
> production CouchDB cluster, I would like to be able to force a field to be
> written to
On Sun, Sep 19, 2010 at 5:37 AM, Jan Lehnardt wrote:
>
> On 14 Sep 2010, at 03:26, J Chris Anderson wrote:
>
>>
>> On Sep 13, 2010, at 6:23 PM, Simon Metson wrote:
>>
>>> Hi James.
>>> I think the thing to do is require that a document has a user field,
>>> and that the value of that field m
On 14 Sep 2010, at 03:26, J Chris Anderson wrote:
>
> On Sep 13, 2010, at 6:23 PM, Simon Metson wrote:
>
>> Hi James.
>> I think the thing to do is require that a document has a user field,
>> and that the value of that field matches the userCtx in the
>> validate_doc_update function. Th
On Sep 13, 2010, at 6:23 PM, Simon Metson wrote:
> Hi James.
> I think the thing to do is require that a document has a user field,
> and that the value of that field matches the userCtx in the
> validate_doc_update function. This then pushes the issue client side, and
> makes the server
Hi James.
I think the thing to do is require that a document has a user field,
and that the value of that field matches the userCtx in the
validate_doc_update function. This then pushes the issue client side,
and makes the servers life easier. It could also be added by the front
end apach
Hi all,
Moving this from the users forum, as it appears what I'm after isn't currently
available. For the security model I with to implement in a production CouchDB
cluster, I would like to be able to force a field to be written to all docs
based on the user context. The _update functionality i
