[
https://issues.apache.org/jira/browse/COUCHDB-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842377#action_12842377
]
Brian Candler commented on COUCHDB-684:
---------------------------------------
> another option would be to add an _id field to the actual JSON response.
> certainly easier, especially for non-Futon clients, but I'm wary about
> "faking" the API so much.
If you were to store a random _rev in the _security object itself, then you
could implement concurrency control for _security without too much work AFAICS.
It would only be half-baked, but since _security doesn't replicate it wouldn't
matter.
Then if you're going to store/update _rev, you might as well set
_id:"_security" at the same time. That is, you wouldn't be faking up the API,
so much as adding some fixed data into _security to make it look more like a
doc.
> Futon security dialog overwrites other properties of security doc
> -----------------------------------------------------------------
>
> Key: COUCHDB-684
> URL: https://issues.apache.org/jira/browse/COUCHDB-684
> Project: CouchDB
> Issue Type: Bug
> Components: Futon
> Affects Versions: 0.11
> Environment: OSX 10.6
> Reporter: David Goodlad
> Attachments: futon_security.patch
>
>
> When the _security document has existing properties other than readers and
> admins, Futon's security dialog will overwrite them. If it's agreed this is
> undesirable behaviour, I'll see about putting a patch together.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
