add "options": {"include_design":true} to your view e.g;
var designDoc = {
_id:"_design/fu",
language: "javascript",
options: {
include_design: true,
},
views: {
data: {"map": map},
}
};
The test design_options.js in Futon has working examples also.
B.
O
Aurélien Bénel writes:
>
>
> >>
> >
> > For example, I modify a _design document in DB1. I then modify the
> > same _design document in DB2. I then replicate DB1 to DB2. I would
> > expect that CouchDB would identify a conflict, however after
> > replication, Couch returns no conflicts in
For example, I modify a _design document in DB1. I then modify the
same _design document in DB2. I then replicate DB1 to DB2. I would
expect that CouchDB would identify a conflict, however after
replication, Couch returns no conflicts in DB2.
Are you sure the replicator connects to th
Jim Z writes:
>
> Does Couch handle conflicts with _design documents or just "regular" design
> documents?
>
>
I am not seeing the same behavior. For example, I modify a _design document in
DB1. I then modify the same _design document in DB2. I then replicate DB1 to
DB2. I would expect that C
a design document is still a document and follows the usual MVCC rules.
B.
On 23 March 2011 15:30, Jim Z wrote:
> Does Couch handle conflicts with _design documents or just "regular" design
> documents?
>
>
Does Couch handle conflicts with _design documents or just "regular" design
documents?
