[
https://issues.apache.org/jira/browse/COUCHDB-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899770#action_12899770
]
Benoit Chesneau commented on COUCHDB-230:
-
actually you could already do :
[
https://issues.apache.org/jira/browse/COUCHDB-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899777#action_12899777
]
Brian Candler commented on COUCHDB-642:
---
I'd prefer that the rev in the URL overrode
Hi all,
I'm writing a custom handler here and for specific reason I want a
continuous replication of one design doc from a db to another db on
the same CouchDB server :
start_replication(Name) -
SourceDb = ?l2b(couch_config:get(myproject, db, somedb)),
{ok, RepDb} =
On Tue, Aug 17, 2010 at 5:24 PM, Wendall Cada wenda...@83864.com wrote:
Often times, I also have an issue with focus on commercial developers.
However, with CouchDB specifically, the commercial developers are also the
most active and helpful community members. Does it make a difference if you
All,
My patch to support the Range header is now on trunk. Attachments are
upgraded for efficient seeking on compaction and do not support the
Range header until that happens. Accept-Ranges: none is returned for
non seekable attachments and Accept-Ranges: bytes is returned for
the new style ones.
[
https://issues.apache.org/jira/browse/COUCHDB-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899817#action_12899817
]
Robert Newson commented on COUCHDB-161:
---
This work is now on trunk.
Range Request
no continuous replication with doc_ids param
Key: COUCHDB-857
URL: https://issues.apache.org/jira/browse/COUCHDB-857
Project: CouchDB
Issue Type: Bug
Affects Versions: 1.0.1, 1.0, 0.11.2,
[
https://issues.apache.org/jira/browse/COUCHDB-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899830#action_12899830
]
Benoit Chesneau commented on COUCHDB-857:
-
behaviour confirmed. I think we should
[
https://issues.apache.org/jira/browse/COUCHDB-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899831#action_12899831
]
Filipe Manana commented on COUCHDB-857:
---
Hi, replication by doc IDs was designed to
[
https://issues.apache.org/jira/browse/COUCHDB-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899832#action_12899832
]
Benoit Chesneau commented on COUCHDB-857:
-
This filter should be created on the
[
https://issues.apache.org/jira/browse/COUCHDB-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899848#action_12899848
]
Klaus Trainer commented on COUCHDB-642:
---
We need to consider that the ETag in the
The reason it you need ?rev= for DELETE is that there's no request
body for DELETE, unlike for PUT. So I don't see that adding ?rev= for
PUT is about consistency. It looks like a neat enhancement, though,
the issues with precedence notwithstanding.
B.
On Wed, Aug 18, 2010 at 2:50 PM, Klaus
Yes, there's no body with DELETE requests. Nonetheless, as with PUT
requests, you can specify the current revision number in the If-Match
header. So, you don't really need ?rev= for DELETE requests.
- Klaus
On Wed, 2010-08-18 at 15:16 +0100, Robert Newson wrote:
The reason it you need ?rev=
Hi Behrad,
I will add test cases to the test harness for multiview and we will
see if we can get this working, the log files help, thanks! Looks like
you are posting as an authenticated user, I haven't tried this with
the multiview, so I will add a test.
I will send you an email later on today
Hi Robert,
I committed that as part of r986710 as it also fixes
support for Safari 5. Thanks for the digging :)
Cheers
Jan
--
On 7 Aug 2010, at 14:36, Robert Newson wrote:
All,
I spent a few hours this morning trying to get the full test suite
running on Chrome. I failed for interesting
secObj as well
On Wed, Aug 18, 2010 at 5:26 PM, Benoit Chesneau bchesn...@gmail.comwrote:
Hi all,
I want to expose the security object to shows, lists, updates and
validate function, so we could eventually add some metadata to a db
(idea come from jcrhis@) . It's relatively easy but I
secObj sounds good
On Wed, Aug 18, 2010 at 5:29 PM, Filipe David Manana
fdman...@apache.org wrote:
secObj as well
On Wed, Aug 18, 2010 at 5:26 PM, Benoit Chesneau bchesn...@gmail.comwrote:
Hi all,
I want to expose the security object to shows, lists, updates and
validate function, so we
+1 for secObj
On Wed, 2010-08-18 at 18:26 +0200, Benoit Chesneau wrote:
Hi all,
I want to expose the security object to shows, lists, updates and
validate function, so we could eventually add some metadata to a db
(idea come from jcrhis@) . It's relatively easy but I hesitate about
the
I have made
http://github.com/normanb/couchdb
which is a fork of the latest couchdb trunk with the multiview code
and tests added.
If geocouch is available then it can still be used.
There are a couple of questions about the multiview on the user /dev
list so I will be adding some more test
On 16 Aug 2010, at 13:00, Benoit Chesneau wrote:
So I've found why 160- test fails from time to time:
Vhosts are loaded at startup when creating the mochiweb loop. So it
only get depending how fast is your machine 1 result and maybe 0 for
really fast machines since the ini isn't defined.
The vhosts refactoring made this issue go away. The underlying problem still
exists in couch_config. It's a race condition
On Aug 18, 2010, at 2:01 PM, Jan Lehnardt wrote:
On 16 Aug 2010, at 13:00, Benoit Chesneau wrote:
So I've found why 160- test fails from time to time:
Vhosts
[
https://issues.apache.org/jira/browse/COUCHDB-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899946#action_12899946
]
Klaus Trainer commented on COUCHDB-642:
---
A use case where being able to specify the
[
https://issues.apache.org/jira/browse/COUCHDB-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899954#action_12899954
]
Benoit Chesneau commented on COUCHDB-230:
-
the $ stuff is already in the code with
GET /db/_design/doc/_info should not trigger an update
--
Key: COUCHDB-858
URL: https://issues.apache.org/jira/browse/COUCHDB-858
Project: CouchDB
Issue Type: Bug
Environment: All
[
https://issues.apache.org/jira/browse/COUCHDB-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899970#action_12899970
]
Ryan Ramage commented on COUCHDB-161:
-
Thanks Robert. This is great work!
Range
Behrad,
I have added http://github.com/normanb/couchdb which contains the
multiview code and javascript tests.
Can you you trying running the multiview js test (right hand side of
futon, select Test Suite) and let me know if this works for you, I
have included a multiview single and multiple
On Wed, Aug 18, 2010 at 9:29 PM, Jan Lehnardt j...@apache.org wrote:
On 18 Aug 2010, at 20:17, Robert Dionne wrote:
The vhosts refactoring made this issue go away. The underlying problem still
exists in couch_config. It's a race condition
The refactoring also added a whole lot of things
actually as things currently stand, it no longer involves 160-* at all.
the issue as I see it is here:
http://github.com/bdionne/couchdb/blob/master/src/couchdb/couch_config.erl#L124
every call to couch_config:set will cause registered notify_funs to be
invoked, *but*, spawned in their own
[
https://issues.apache.org/jira/browse/COUCHDB-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaus Trainer updated COUCHDB-858:
--
Attachment: 0001-Don-t-trigger-a-view-update-when-sending-a-GET.patch
Here the relevant piece
[
https://issues.apache.org/jira/browse/COUCHDB-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12900020#action_12900020
]
Adam Kocoloski commented on COUCHDB-858:
Thanks, that patch is exactly what I was
30 matches
Mail list logo
