Re: Commits to the wrong list?

Thank you Jan -Filippo > On 17 Mar 2017, at 13:53, Jan Lehnardt <j...@apache.org> wrote: > > Oh, I was told this was fixed already. > > I’m on it. > > Best > Jan > -- >> On 17 Mar 2017, at 14:45, Filippo Fadda <filippo.fa...@programmazione.it

Re: Commits to the wrong list?

> Best > Jan > -- > PS: We’re not all guys here. >> On 9 Mar 2017, at 15:41, Filippo Fadda <filippo.fa...@programmazione.it> >> wrote: >> >> Hi guys, >> >> since yesterday I’m receiving a ton of e-mails from GitHub. Perhaps I should &g

Commits to the wrong list?

Hi guys, since yesterday I’m receiving a ton of e-mails from GitHub. Perhaps I should receive these e-emails because I have subscribed to comm...@couchdb.apache.org , but I have not. Cheers -Filippo

Re: View Processing Pipeline Architecture

When you query a view all the new documents since the last update (of the view itself) are indexed. Not only the single view, but also all the other views contained inside the same design document are updated. Keep in mind it when you decide the place to store the views. That’s the way it

Re: CouchDB minor release

And well, "Configuration | Main config" doesn’t display the configuration. If you click on “Configuration | CORS” and then again on “Main config” it doesn’t display the configuration. It’s a small issue. > On 10 Oct 2016, at 19:03, Robert Samuel Newson wrote: > > Hi, > >

Re: CouchDB minor release

I have just found a bug. On a fresh installation, just after you “fix the admin party” in Fauxton, if you try to create a new database or configure the server (cluster or single node) Futon gives you an error (in case of db creation) or it simply doesn’t proceed (single node config). To

Re: CouchDB Next

My bad Jan, I didn’t read this paragraph "GET/DELETE accordingly”, so I have thought it was just for updates. -Filippo

Re: CouchDB Next

Well, that's not what I meant. What I want is a query parameter to get only the specified document’s fields on a simple GET /{db}/{docid}. CouchDB should parse the JSON and returns only the required fields, because in a real scenario there are times you don’t need the entire document, but just

Re: CouchDB Next

First of all thank you for CouchDB 2.0! I would like to add some thoughts if I may. I have been working for a long time with CouchDB, and I think 2.0 is a great step ahead, but I like to address some obstacles I have found during the development of a social network platform with versioning

[jira] [Commented] (COUCHDB-2222) Design document name doesn't show on active tasks

[ https://issues.apache.org/jira/browse/COUCHDB-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970055#comment-13970055 ] Filippo Fadda commented on COUCHDB-: The screenshot is attached

[jira] [Created] (COUCHDB-2222) Design document name doesn't show on active tasks

Filippo Fadda created COUCHDB-: -- Summary: Design document name doesn't show on active tasks Key: COUCHDB- URL: https://issues.apache.org/jira/browse/COUCHDB- Project: CouchDB

Re: [PROPOSAL] new underscore namespacing

I like this idea. -Filippo On Dec 3, 2013, at 3:16 PM, Robert Newson wrote: I like the idea, though I remember a suggestion to lift all of these things out of the bodies entirely (I'm thinking mostly of _id and _rev) and into request/response headers. This has other advantages (we wouldn't

Re: [discuss] couchapp.org down, couchapp.org spammed

On Dec 1, 2013, at 4:26 AM, Alexander Shorin wrote: You can do the same with Erlang query server since it has access to all internal functions. I can do it in PHP inside my Query Server (I already said this to you), without the need to investigate the CouchDB internals, trying to find the

Re: [discuss] couchapp.org down, couchapp.org spammed

I'm not a neophyte, I have just a different opinion of yours. Republicans and democrats don't share same opinions, and even inside a group you can find people with different opinions and you have to respect them, always. This is called democracy. I don't decide the goals myself, but I can

Re: [discuss] couchapp.org down, couchapp.org spammed

I can understand your frustration but I see other members are avoiding your question because they don't want take a position (or maybe hurt your feelings?). Dirkjan is the only one has taken a position and, personally, I agree with him, but you already know that since we discussed, partially,

Re: [discuss] couchapp.org down, couchapp.org spammed

David, for me, and I speak just for myself, CouchDB is a database. And IMHO couch apps are something that shouldn't be part of the CouchDB core. Benoit asked a very simple question and I gave my opinion. I think who matters should take a position on the subject because I can understand Benoit

Re: [discuss] couchapp.org down, couchapp.org spammed

Alexander, PgREST is not PostgreSQL anyway, it's a project that uses PostgreSQL and I think CouchApp should be the same, maybe a plugin but not a core feature. Which are the CouchDB goals? The goals are determined at blastoff time. You must ensure the goals are reasonable, attainable, simply

Re: [discuss] couchapp.org down, couchapp.org spammed

List and show are not stored procedure. We already discussed that Benoit. http://wiki.apache.org/couchdb/Formatting_with_Show_and_List From the documentation: Show and list functions are side effect free and idempotent. They can not make additional HTTP requests against CouchDB. Their purpose

Re: [discuss] couchapp.org down, couchapp.org spammed

On Dec 1, 2013, at 1:18 AM, Benoit Chesneau wrote: And you keep ignoring what I said about the doc. Ie. it is not complete (and it must be fixed). Like stored procedure they are stored. Like stored procedure they can be used in a query. Afaik queries happen on HTTP level in couchdb.

Re: Suggested process for integrating l10n into the CouchDB source

On Nov 6, 2013, at 10:23 PM, Andy Wenk wrote: http://docs.couchdb.org/en/latest - default English http://docs.de.couchdb.org/en/latest - German http://docs.ru.couchdb.org/en/latest - Russian Honestly, terrible. Is possible something like this? Not the best but a viable solution.

Re: Elixir Sandbox

Sandboxing is something optional I think, you need only when you are developing a CouchApp, when you do all in JavaScript, using the _users database and running the app inside CouchDB. But if you are just using CouchDB like a database, developing a web app using PHP or Python, for example,

Re: Elixir Sandbox

Sandboxing is useful when you are running applications, in a defined environment (like an OS), you can't trust, not libraries, but applications. For example in iOS all the apps are sandboxed, not the system libraries. But no one can't run an application inside CouchDB if CouchDB can't be

Re: Elixir Sandbox

But you should be able to create a view and save it into a ddoc. And to do that you need the access to the database and the user credentials. If the web application is made in Python, for example, you don't even know it's using CouchDB, how can you think to create a view? This is just science

Re: [MERGE] 1781 Reorganize and improve docs

Did you commit my last changes? I had fix several typos and formatting issues. Bye -Filippo On Sep 28, 2013, at 2:48 PM, Alexander Shorin wrote: Hi devs! There was big docs merge from 1781-reorganize-and-improve-docs branch into the master branch. What's happened? === Changes - New

Re: [MERGE] 1781 Reorganize and improve docs

I did a second PR, I'm not sure you merged it. Sent from my iPhone On 01/ott/2013, at 18:53, Alexander Shorin kxe...@gmail.com wrote: On Tue, Oct 1, 2013 at 8:49 PM, Filippo Fadda filippo.fa...@programmazione.it wrote: Did you commit my last changes? I had fix several typos and formatting

Re: [1.4] Binaries for the release

it launched at logon? What's the normal UX pattern for OSX user daemons? A+ Dave On 30 August 2013 13:46, Filippo Fadda filippo.fa...@programmazione.it wrote: it works for me, but a thing I don't like is that when you run the app, it doesn't appear on the dock and to quit you have to use

Re: [jira] [Commented] (COUCHDB-906) Please offer offline downloadable documentation

+1 Just link them. On Aug 26, 2013, at 5:45 PM, Noah Slater (JIRA) wrote: [ https://issues.apache.org/jira/browse/COUCHDB-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750157#comment-13750157 ] Noah Slater commented on COUCHDB-906:

[jira] [Created] (COUCHDB-1877) There is a typo in --db-dir description

Filippo Fadda created COUCHDB-1877: -- Summary: There is a typo in --db-dir description Key: COUCHDB-1877 URL: https://issues.apache.org/jira/browse/COUCHDB-1877 Project: CouchDB Issue Type

[jira] [Commented] (COUCHDB-1877) There is a typo in --db-dir description

[ https://issues.apache.org/jira/browse/COUCHDB-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13747608#comment-13747608 ] Filippo Fadda commented on COUCHDB-1877: I don't know which file I have

[jira] [Commented] (COUCHDB-1877) There is a typo in --db-dir description

[ https://issues.apache.org/jira/browse/COUCHDB-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13747616#comment-13747616 ] Filippo Fadda commented on COUCHDB-1877: Thx, I have done the PR

[jira] [Commented] (COUCHDB-1868) Using multiple keys, the _all_docs built-in view acts differently then a user defined view

[ https://issues.apache.org/jira/browse/COUCHDB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738070#comment-13738070 ] Filippo Fadda commented on COUCHDB-1868: OK, Robert might be right, we can only

[jira] [Created] (COUCHDB-1868) Using multiple keys, the _all_docs built-in view acts differently then a user defined view

Filippo Fadda created COUCHDB-1868: -- Summary: Using multiple keys, the _all_docs built-in view acts differently then a user defined view Key: COUCHDB-1868 URL: https://issues.apache.org/jira/browse/COUCHDB-1868

[jira] [Commented] (COUCHDB-1868) Using multiple keys, the _all_docs built-in view acts differently then a user defined view

[ https://issues.apache.org/jira/browse/COUCHDB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737049#comment-13737049 ] Filippo Fadda commented on COUCHDB-1868: OK, I got your point. Now

[jira] [Issue Comment Deleted] (COUCHDB-1868) Using multiple keys, the _all_docs built-in view acts differently then a user defined view

[ https://issues.apache.org/jira/browse/COUCHDB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filippo Fadda updated COUCHDB-1868: --- Comment: was deleted (was: Please look here: http://pastebin.com/h1sYBw47) Using

[jira] [Commented] (COUCHDB-1868) Using multiple keys, the _all_docs built-in view acts differently then a user defined view

[ https://issues.apache.org/jira/browse/COUCHDB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737063#comment-13737063 ] Filippo Fadda commented on COUCHDB-1868: Please look here: http://pastebin.com

Re: [jira] [Commented] (COUCHDB-1868) Using multiple keys, the _all_docs built-in view acts differently then a user defined view

Sorry for the mess guys, I saw formatting issues so I posted using pastebin and I deleted the comment, adding a new one. -Filippo On Aug 12, 2013, at 7:20 PM, Filippo Fadda (JIRA) wrote: [ https://issues.apache.org/jira/browse/COUCHDB-1868?page

[jira] [Commented] (COUCHDB-1868) Using multiple keys, the _all_docs built-in view acts differently then a user defined view

[ https://issues.apache.org/jira/browse/COUCHDB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737160#comment-13737160 ] Filippo Fadda commented on COUCHDB-1868: 1) Agree 100%. 2) Sure. 3) _all_docs

[jira] [Commented] (COUCHDB-1868) Using multiple keys, the _all_docs built-in view acts differently then a user defined view

[ https://issues.apache.org/jira/browse/COUCHDB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737189#comment-13737189 ] Filippo Fadda commented on COUCHDB-1868: Thank you, I will do the patch

[jira] [Commented] (COUCHDB-1868) Using multiple keys, the _all_docs built-in view acts differently then a user defined view

[ https://issues.apache.org/jira/browse/COUCHDB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737509#comment-13737509 ] Filippo Fadda commented on COUCHDB-1868: OK, I think I got the snippets I should

[jira] [Commented] (COUCHDB-1868) Using multiple keys, the _all_docs built-in view acts differently then a user defined view

[ https://issues.apache.org/jira/browse/COUCHDB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737632#comment-13737632 ] Filippo Fadda commented on COUCHDB-1868: Who, or what, is actually impacted

Re: couchDB with jsp

http://wiki.apache.org/couchdb/Getting_started_with_Java On Aug 9, 2013, at 7:56 AM, sagar kokate wrote: Dear Sir, Can u please tell me how to connect jsp code with couchDB. Can u provide code for that.I am in the great need of that.Which driver is it requiring for the connection.

Re: [REVIEW] Docs update

Done. I don't know much about Homebrew, but it seems to me that you don't need all the steps described to install CouchDB from brew. Someone should also revise the Homebrew section. Actually the Installation of Unix-like systems is full of you are driving me crazy things. I didn't try, but I'm

Re: [REVIEW] Docs update

On Aug 5, 2013, at 8:01 PM, Noah Slater wrote: MacPorts is a POS. We should completely avoid mentioning it. (Both in the binary install section, and in the source install section.) OMG, the POS is brew not MacPorts. All my system is installed around MacPorts, even Apache (sure I replaced the

Re: [REVIEW] Docs update

Hi Alexander, glad to know about changes, but... I don't understand why the installation section is so much complicated. You just need a command to install CouchDB on the most Linux distro or Mac OS X. To understand that, a user have to read also the Community installation guides present in

Re: [REVIEW] Docs update

On Jul 25, 2013, at 12:44 AM, Alexander Shorin wrote: That's why installation guides (from sources, using system package manager etc.) have to be in docs. I'm not telling they shouldn't be there, I'm telling, in the doc, you want find all: - Mac OS X Download the image (with the link

Re: [REVIEW] Docs update

On Jul 25, 2013, at 2:38 AM, Alexander Shorin wrote: To keep there - you mean wiki? At this you're also right: once docs be merged with master, wiki content have to redirect to docs for some time before fade away. Good to know. :-) P.S. I also will be glad if you take a look on query server

Re: Releasing experimental features (was: Re: [PROPOSAL] Port _db_updates from rcouch to master)

Experimental in PHP is used for extensions that are not bundled with PHP. Instead deprecated is used to inform the user that a function shouldn't be used anymore. In the same way CouchDB could inform that an API is deprecated or experimental. 1) X-Couch-Deprecated 2) X-Couch-Experimental

Re: Releasing experimental features (was: Re: [PROPOSAL] Port _db_updates from rcouch to master)

On Jul 22, 2013, at 12:13 PM, Alexander Shorin wrote: Experimental features should be enabled in configs so user takes responsibility for any behavior it provides. I don't agree because when a feature is not experimental anymore you have to remove it from the experimental list and that can

Re: Releasing experimental features (was: Re: [PROPOSAL] Port _db_updates from rcouch to master)

I'm in doubt about X-Couch-Experimental header. If for X-Couch-Deprecated client library __may__ raise some warning about hey, resource you're requested is deprecated! alarm! alarm!, what the reaction should be for X-Couch-Experimental? There couldn't be any warnings, because I'm explicitly

Re: Releasing experimental features (was: Re: [PROPOSAL] Port _db_updates from rcouch to master)

HI Jan, so the differences with _changes are: 1) there is no normal feed, continuous is default; 2) hearbeat is not supported for continuous or longpoll feeds; 3) feed style option is not supported; 4) since option is not supported; 5) limit option is not supported; 6) descending option is not

[jira] [Created] (COUCHDB-1857) _changes API documentation doesn't mention the eventsource feed

Filippo Fadda created COUCHDB-1857: -- Summary: _changes API documentation doesn't mention the eventsource feed Key: COUCHDB-1857 URL: https://issues.apache.org/jira/browse/COUCHDB-1857 Project

Re: Releasing experimental features (was: Re: [PROPOSAL] Port _db_updates from rcouch to master)

5. yes, can't exist we are speaking about deb events 6. correct, we are speaking about events 7) yup others are true On Mon, Jul 22, 2013 at 3:58 PM, Filippo Fadda filippo.fa...@programmazione.it wrote: HI Jan, so the differences with _changes are: 1) there is no normal feed

Re: Releasing experimental features (was: Re: [PROPOSAL] Port _db_updates from rcouch to master)

Thx, added the support for this API to ElephantOnCouch. -Filippo On Jul 22, 2013, at 8:29 PM, Jan Lehnardt wrote: On 22.07.2013, at 19:23, Filippo Fadda filippo.fa...@programmazione.it wrote: 2) heartbeat is not expressed in milliseconds like for _changes, but you can pass just true

[jira] [Created] (COUCHDB-1858) X-Couch-Full-Commit is not mentioned in _bulk_docs API

Filippo Fadda created COUCHDB-1858: -- Summary: X-Couch-Full-Commit is not mentioned in _bulk_docs API Key: COUCHDB-1858 URL: https://issues.apache.org/jira/browse/COUCHDB-1858 Project: CouchDB

[jira] [Commented] (COUCHDB-1858) X-Couch-Full-Commit is not mentioned in _bulk_docs API

[ https://issues.apache.org/jira/browse/COUCHDB-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13715841#comment-13715841 ] Filippo Fadda commented on COUCHDB-1858: Alexander, the description is also

Re: [jira] [Commented] (COUCHDB-1744) Make the config file optional

IMO, instead of default.ini and local.ini we should have something like couchdb.ini and couchdb.ini-default or couchdb-default.ini, so you don't need to read the documentation to understand what they do, because their name are self-explaining. -Filippo On Jul 7, 2013, at 2:05 AM, Alexander

[jira] [Commented] (COUCHDB-1254) Document design and view options

[ https://issues.apache.org/jira/browse/COUCHDB-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13696756#comment-13696756 ] Filippo Fadda commented on COUCHDB-1254: From my library: //! @brief Causes map

Re: Fauxton Tidings

I Like it very much. :-) When Fauxton will replace Futon? 1.4? On Jun 19, 2013, at 9:38 PM, Russell Branca wrote: Looks like I tried to get too fancy with embedding dropbox images. Here's public urls viewable on dropbox.com: all dbs:

Re: Getting rid of file lists in documentation Makefiles

On May 21, 2013, at 5:00 PM, Jan Lehnardt wrote: I want to start a section in there that is called “The Developer Handbook”. +1 -Filippo

Re: wiki choice: moinmoin vs confluence

The documentation in the source is a great idea, and it's great having it in Futon. In my opinion the wiki is superfluous and should be removed. My 2 cents. -Filippo

Re: [VOTE] Merge BigCouch

+1

[jira] [Created] (COUCHDB-1594) Incoherent behavior when delete attachments

Filippo Fadda created COUCHDB-1594: -- Summary: Incoherent behavior when delete attachments Key: COUCHDB-1594 URL: https://issues.apache.org/jira/browse/COUCHDB-1594 Project: CouchDB Issue

[jira] Commented: (COUCHDB-946) Calling the /_restart API via socket or cURL, sometimes CouchDB restarts before I can get the response headers.

[ https://issues.apache.org/jira/browse/COUCHDB-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12935918#action_12935918 ] Filippo Fadda commented on COUCHDB-946: --- I will. Calling the /_restart API via

[jira] Created: (COUCHDB-967) CouchDB create database response error is wrong

Affects Versions: 1.0.2, 1.1, 1.2, 2.0 Environment: Mac OS X Snow Leopard Reporter: Filippo Fadda Priority: Minor When you try to create a database with a / inside name, the following error is returned. For example

[jira] Commented: (COUCHDB-947) /_restart API requires Content-Type: application/json

[ https://issues.apache.org/jira/browse/COUCHDB-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932532#action_12932532 ] Filippo Fadda commented on COUCHDB-947: --- Good point Jan, I agree. Maybe we should

[jira] Updated: (COUCHDB-946) Calling the /_restart API via socket or cURL, sometimes CouchDB restarts before I can get the response headers.

[ https://issues.apache.org/jira/browse/COUCHDB-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filippo Fadda updated COUCHDB-946: -- Fix Version/s: 1.2 Calling the /_restart API via socket or cURL, sometimes CouchDB restarts

[jira] Updated: (COUCHDB-947) /_restart API requires Content-Type: application/json

[ https://issues.apache.org/jira/browse/COUCHDB-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filippo Fadda updated COUCHDB-947: -- Fix Version/s: 1.2 /_restart API requires Content-Type: application/json

[jira] Updated: (COUCHDB-946) Calling the /_restart API via socket or cURL, sometimes CouchDB restarts before I can get the response headers.

[ https://issues.apache.org/jira/browse/COUCHDB-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filippo Fadda updated COUCHDB-946: -- Fix Version/s: 1.0.1 1.1 Affects Version/s: (was: 1.0.1