I'm +1 on this as well.
The new extra field in #user_ctx only needs to have a valid EJSON
value. It's default value could be the atom 'null'.
Check json_user_ctx/1 in src/couchdb/couch_util.erl.
On Fri, Dec 3, 2010 at 6:28 PM, Adam Kocoloski wrote:
> +1 from me. I'm pretty sure nothing would bre
+1 from me. I'm pretty sure nothing would break if a field was added to
#user_ctx{}, and adding an 'aux' field that would host a proplist is a nice way
to avoid having to make lots of little changes to the record in the future.
Adam
On Dec 3, 2010, at 12:04 PM, Alen Mujezinovic wrote:
> Hey g
Hey guys
Here's a suggestion about the `user_ctx` record in couch_db.hrl:
We've been working on custom authentication handlers and one issue came
up to pass some custom information into `validate_doc_update`.
We're essentially having a bunch of databases, each of which holds
documents with user
