[
https://issues.apache.org/jira/browse/COUCHDB-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Davies updated COUCHDB-260:
-
Attachment: list_reduce_views.3.diff
Added fix and tests for bug when _list is empty (i.e.
On 23.02.2009, at 10:20, Jan Lehnardt wrote:
On 22 Feb 2009, at 23:30, Noah Slater wrote:
On Sun, Feb 22, 2009 at 05:47:00PM +0100, Jan Lehnardt wrote:
It looks like we have a draw with weigh-in from the community
on a +1 to accept the patch.
We need more discussion here.
Oh wow, I was
Hi Christopher,
On 23 Feb 2009, at 10:31, Christopher Lenz wrote:
Personally, I don't think this whole thing is very important, but I
don't see any harm in adding the trailing newline right now.
Me neither. The only thing is that it changes the API and we agreed to
solve these issues within
This is a very common misconception about the revision system. Any
ideas how we can make this better?
random ideas:
- Remove the ability to get old revisions
- Make it much harder/verbose to get old revision
- Make the api to get old revisions something like ?
- Don't call them revisions, call them turd blossoms or hobo socks.
People won't know what they are, but at least they won't misuse them.
+1 as revision is too tied up to CVS and friends. I'm no so sure about
turd blossoms though ;)
U
Hi,
On 23 Feb 2009, at 15:16, Damien Katz wrote:
This is a very common misconception about the revision system. Any
ideas how we can make this better?
random ideas:
- Remove the ability to get old revisions
- Make it much harder/verbose to get old revision
- Make the api to get old
On Feb 23, 2009, at 9:16 AM, Damien Katz wrote:
This is a very common misconception about the revision system. Any
ideas how we can make this better?
random ideas:
- Remove the ability to get old revisions
+1
- Make it much harder/verbose to get old revision
- Make the api to get old
On 22 Feb 2009, at 15:06, Jan Lehnardt wrote:
I mentioned this in an earlier mail but I'd like to bring it up again,
since your input is needed here. Metrics are identified with a
tuple `{Module, Key}`. `Module` is the module that initiates the
counting of the metric and `Key` is a uniquely
On Mon, Feb 23, 2009 at 6:16 AM, Damien Katz dam...@apache.org wrote:
This is a very common misconception about the revision system. Any ideas how
we can make this better?
random ideas:
- Don't call them revisions, call them turd blossoms or hobo socks.
People won't know what they are, but
For a reminder :
revision (n)
1. the act or process of revising,
2. a corrected or new version of a book, article, etc.
For me this term is correct with the use in Couch
I think a good explanation of what a compaction/replication are doing (ie
removing old rev, or replicating only current
On 23 Feb 2009, at 16:11, Patrick Antivackis wrote:
For a reminder :
revision (n)
1. the act or process of revising,
2. a corrected or new version of a book, article, etc.
For me this term is correct with the use in Couch
Damien is not saying the usage is wrong in CouchDB, but people
On 23 Feb 2009, at 16:40, Patrick Antivackis wrote:
May be i can start a wiki page on replication, but i think the
http://couchdb.apache.org/docs/overview.html should be clarified too.
Hey yeah, feel free to add new pages and fi existing ones as you
see fit, thanks! :)
Cheers
Jan
--
(Still
On Mon, Feb 23, 2009 at 10:20:12AM +0100, Jan Lehnardt wrote:
Now I'm confused, you wrote, but didn't send the RESULT mail? :)
I had replied, but managed to reply to myself instead of the list.
--
Noah Slater, http://tumbolia.org/nslater
[
https://issues.apache.org/jira/browse/COUCHDB-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Joseph Davis closed COUCHDB-265.
-
Resolution: Invalid
Fix Version/s: 0.9
Should've read the spec before filing :D
[
https://issues.apache.org/jira/browse/COUCHDB-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12676075#action_12676075
]
Jens Alfke commented on COUCHDB-265:
By the way, curl has exactly the same problem
On Mon, Feb 23, 2009 at 10:30 AM, Jan Lehnardt j...@apache.org wrote:
On 23 Feb 2009, at 16:11, Patrick Antivackis wrote:
For a reminder :
revision (n)
1. the act or process of revising,
2. a corrected or new version of a book, article, etc.
For me this term is correct with the use in
On 24/02/2009, at 9:32 AM, Dean Landolt wrote:
Can you suggest how we improve the wiki docs to satisfy this? In my
opinion, the docs are clear* and the term is overloaded and
confusing.
* http://wiki.apache.org/couchdb/Document_revisions has
You cannot rely on document revisions for any
On 24/02/2009, at 12:15 PM, Chris Anderson wrote:
Would it be overly difficult to just add in the ability to keep a
full rev
history based on a config setting?
This would be a pretty big change. As Antony says, once you go down
that path a little, you end up at something that is not really
On Feb 23, 2009, at 8:45 PM, Chris Anderson wrote:
Would it be overly difficult to just add in the ability to keep a
full rev
history based on a config setting?
This would be a pretty big change. As Antony says, once you go down
that path a little, you end up at something that is not
On Mon, Feb 23, 2009 at 6:30 PM, Damien Katz dam...@apache.org wrote:
Maybe we should change that use from ?rev... to ?conflict=
If we follow your _cc idea, we could change from ?rev= to ?cc=
I think if we change from _rev to something else, _cc for concurrency
control is good. I'm not sure
On 24/02/2009, at 1:39 PM, Jeff Hinrichs - DMT wrote:
scenario, master-slave -- slaves only keep the most recent, while the
master keeps complete. conflict resolution is handled solely by the
master.
scenario, first-among-equals -- multi-master where a single master is
used as the basis for
21 matches
Mail list logo
