wohali commented on issue #2015:
URL: https://github.com/apache/couchdb/issues/2015#issuecomment-650356192
For the record, I don't care one way or the other, but if this is a use
case we're going to explicitly support, it deserves to be documented
correctly, along with any limitation
wohali commented on issue #2015:
URL: https://github.com/apache/couchdb/issues/2015#issuecomment-649740347
bump on this. @garrensmith @rnewson Are we going to prevent user-defined
`_rev` values in fdb-based CouchDB? This issue makes it clear it could be a
"sharp edge" that users could get
wohali commented on issue #2015: parse_revid - Badarg error in HTTP request
URL: https://github.com/apache/couchdb/issues/2015#issuecomment-598953820
@rnewson @davisp @janl In light of 4.0 development, we should decide one way
or the other on this.
In short: are we going to allow us
wohali commented on issue #2015: parse_revid - Badarg error in HTTP request
URL: https://github.com/apache/couchdb/issues/2015#issuecomment-487318218
@rnewson My $0.02:
* We never said whether we allow or disallow changing the revid, either in
the replicator spec or the docs.
* 2.x (
wohali commented on issue #2015: parse_revid - Badarg error in HTTP request
URL: https://github.com/apache/couchdb/issues/2015#issuecomment-486423336
Are you really making your own _rev tokens? That's pretty far outside the
supported API.
--
