Answer to this question should be pretty straigthforward given they always
have lived together.
But here I would like you to reflect on their concepts, in order to draw a
line on what is the real innovating feature couchdb should point on for the
future.
Imho couchdb replication is simply awesome
Jan.. don't you think you are simply too biased for external projects, such
as your hoodie and pouchdb, to choose by your own, on a topic like
'retiring couchapps', so important to couchdb users and devs?
You REALLY can't mask it behind a marketing@ decision, of finding a story
you have already wr
Github user benkeen commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/391#issuecomment-99627486
Since Garren's away the rest of the week, I'm going to finish this PR here:
https://github.com/apache/couchdb-fauxton/pull/399
---
If your project is set up for
GitHub user benkeen opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/399
Fixing view bugs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/benkeen/couchdb-fauxton fixing-view-bugs
Alternatively you can review
Github user michellephung commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/391#issuecomment-99523820
i've noticed two things.
1. Uncaught TypeError: this._collection.hasPrevious is not a function <--
happens when i save a view, then try to use the
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/391#issuecomment-99516320
https://cloudup.com/c0VbKefzH9R
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pr
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/391#issuecomment-99515642
video soon
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have t
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/391#issuecomment-99515622
i am getting race conditions
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proje
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/397#issuecomment-99514801
+1 great!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have th
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/398#issuecomment-99514664
merged as 4730b1144c59c9de7edb29b5eafe95e19edbcae2
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user robertkowalski closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/398
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if th
Github user robertkowalski commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/391#discussion_r29767681
--- Diff: app/addons/documents/tests/viewIndex.componentsSpec.react.jsx ---
@@ -179,12 +172,12 @@ define([
afterEach(funct
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-couch/pull/47#issuecomment-99484616
Could you rebase your PR for no-ff merge?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pro
Github user iilyak commented on the pull request:
https://github.com/apache/couchdb-couch/pull/19#issuecomment-99483638
All unrelated commits are removed. PR is rebased against current master.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb-couch/pull/19#discussion_r29760699
--- Diff: src/couch_db_updater.erl ---
@@ -605,10 +605,41 @@ init_db(DbName, Filepath, Fd, Header0, Options) ->
Db
end.
> On 06 May 2015, at 15:34, Katharina Jockenhöfer
> wrote:
>
> Hi all,
> I am putting together the weekly news for tomorrow. Send me your submissions,
> if you have any.
>
> On timings in general (FYI) - If you want to make sure that news get
> included, I try and prepare them for Thursdays,
Github user iilyak commented on a diff in the pull request:
https://github.com/apache/couchdb-couch/pull/19#discussion_r29758581
--- Diff: src/couch_db_updater.erl ---
@@ -605,10 +605,41 @@ init_db(DbName, Filepath, Fd, Header0, Options) ->
Db
end.
Hi all,
I am putting together the weekly news for tomorrow. Send me your submissions,
if you have any.
On timings in general (FYI) - If you want to make sure that news get included,
I try and prepare them for Thursdays, some point between early afternoon and
later evening - depending on my othe
Github user garrensmith commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/397#issuecomment-99457014
@robertkowalski I've removed the PouchDBCollection
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user sebastianrothbucher commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#issuecomment-99413729
K, great
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not hav
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#issuecomment-99407635
hey @sebastianrothbucher i think after you fixed the last two small issues
and rebased the branch we can merge it
---
If your project is set up for it, y
21 matches
Mail list logo
