| commit | 4eea9571171a5b41d832da32204a1122a01f4b0e | [log] [tgz] |
|---|---|---|
| author | ILYA Khlopotov <iilyak@ca.ibm.com> | Fri Aug 26 02:00:41 2016 -0700 |
| committer | ILYA Khlopotov <iilyak@ca.ibm.com> | Fri Aug 26 02:00:41 2016 -0700 |
| tree | 46bec401411830815c938d7f7cea292808dd8626 | |
| parent | 39ef15a28e5be1d697c7c29dd64fcc18c24e7881 [diff] | |
| parent | 0756d35ac8b091aa1eda1909cd231c447d8bbd8e [diff] |
Merge remote branch 'cloudant:3102-fix-number-of-elements' This closes #2 Signed-off-by: ILYA Khlopotov <iilyak@ca.ibm.com>
couch_peruser is a CouchDB daemon that ensures that a private per-user database exists for each document in _users. These databases are writable only by the corresponding user. Databases are in the form:
userdb-{hex encoded username}
For example, the user bob will have a database named userdb-626f62.
The reason for hex encoding is that CouchDB usernames have no restrictions, but CouchDB databases have restrictions. Hex encoding the UTF-8 representation of the username is a transformation that's easy to correctly implement in just about any language, especially JavaScript and Erlang. Other encodings would be possible, but would require additional client and server-side code to support that encoding. This is the simplest scheme that is obviously correct.