Hi Couchers,
we're getting into a phase where CouchDB is distributed in software
distributions (like Ubuntu) with long term support on the distributors
end. While this is in theory none of our concern, we probably want
to make sure our future is as smooth as theirs (i.e. users are likely
to come
On Wed, Jul 15, 2009 at 17:57, Jan Lehnardtj...@apache.org wrote:
If you like temp views, I'd like to take your concerns into consideration.
I like testing out views from Futon, but it seems you're going to keep
that anyway. I wonder if keeping a somewhat-compatible copy of the
Couch API in JS
I like temp views. It was how I got started with couch as it was easy
to experiment with the knowledge that it was going to be slow for
large documents. It's possible in Futon to have a warning message (big
bold blinking red font) that indicates that this is for
experimentation and not for
I like the idea of removing temp view code a lot. The last time I
remember this conversation it was basically limited by the fact that
we wanted to keep supporting temp_views so that new users could use
them to learn CouchDB. What we didn't have before were index files
named after signatures. With
Hi Kowsik,
Thanks for your feedback :)
On 15 Jul 2009, at 18:29, kowsik wrote:
I like temp views. It was how I got started with couch as it was easy
to experiment with the knowledge that it was going to be slow for
large documents. It's possible in Futon to have a warning message (big
bold
Hi Paul,
thanks :)
On 15 Jul 2009, at 18:33, Paul Davis wrote:
I like the idea of removing temp view code a lot.
I remember you saying that it'd remove some significant amount
of code out of the view server. This is something that should be
considered, too.
The last time I
remember this
Hi,
I'm thinking something along the lines of having the Futon interface
create _design documents that include a futon: true member so that
we can filter them out in other parts of the interface, plus a list of
Old temp views that you could pull up and edit. This would also give
us the ability
On Wed, Jul 15, 2009 at 12:43 PM, Jan Lehnardtj...@apache.org wrote:
Hi Paul,
thanks :)
On 15 Jul 2009, at 18:33, Paul Davis wrote:
I like the idea of removing temp view code a lot.
I remember you saying that it'd remove some significant amount
of code out of the view server. This is
[
https://issues.apache.org/jira/browse/COUCHDB-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Lehnardt reassigned COUCHDB-413:
Assignee: Noah Slater
src/couchdb/priv/couchspawnkillable not included by make dist
[
https://issues.apache.org/jira/browse/COUCHDB-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Lehnardt reassigned COUCHDB-414:
Assignee: Noah Slater
If aclocal is invoked during build, it doesn't get called with the
Hi,
I've created an interface for _list functions based on the _view code.
Please have a look, the code is at GitHub [0].
In case you don't want to clone it with git, you can also download the
share/ folder and unpack it over your current source. Click on the
download button at the top [1].
On Wed, Jul 15, 2009 at 10:11 PM, Mark Hammondskippy.hamm...@gmail.com wrote:
On 16/07/2009 1:57 AM, Jan Lehnardt wrote:
A feature I am not comfortable with is temp views. The approach
renaming them with slow views didn't pan out so I'm proposing to get
rid of them all together.
I quite
12 matches
Mail list logo
