I am a huge +1 this behaviour, ie not failing queries, use a slow full
table scan if needed and warn users
that they should create an index. This allows people to easily start
constructing and improving their query
without having to presetup their query with indexes before they know what
query they
Having a master version available does not seem to break those policies
(advertising outside the development community seems purposefully vague),
and if it did then those policies should be fixed. A master version of
CouchDB available for testing with PouchDB would be hugely beneficial, I
imagine f
+1, have found this useful / necessary with PouchDB over the years
Describing our workflow as it may be useful (its also very similiar to
mozillas). We have Tier 1
supported platform, node stable, stable releases of browsers etc a checkin
is not allowed to make
those go red, if something lands tha
ver.
>
> n=1 && q=1 might work as a side-effect, but not sure how that is useful
> for reliable tests :)
>
> Best
> Jan
> --
>
>
> >
> > On 2 September 2016 at 10:53, Jan Lehnardt wrote:
> >>
> >>> On 02 Sep 2016, at 11:45, Dale Harve
In PouchDB we used to generate unique database names for tests, however we
removed it for serveral reasons, one large reason being it indicates a race
condition in critical code if we cannot reliably create -> delete -> create
the same database (we have uncovered and fixed a lot of bugs in PouchDB
So I was wondering about the capabilities of built in filters, whether
mango based ones or otherwise.
I would like to add an option to PouchDB replication that only replicates
the currently active documents but still handles deletions properly, so
basically implementing a filter that ignored any d
I would really like to give users better abilities to handle conflict
resolution, I am however extremely worried about considering to introduce
another API endpoint. We have like 6/7 read API's each of them having their
own idiosyncrasies and its extremely confusing for users to know which to
use w
I havent yet started looking into the implementation details, but when
using pouchdb-find I have very much always expected that at some point we
would analyse the queries and automatically produce an index for them. This
seems like a great step in between.
On 4 January 2016 at 13:27, Robert Kowals
hanks and best regards,
> Johs
>
>
> > On 20 Oct 2015, at 11:10, Dale Harvey wrote:
> >
> > This discussion has gone round and round a couple of times in different
> > forms
> > so I will avoid repeating my previous points but from working on PouchDB,
&g
This discussion has gone round and round a couple of times in different
forms
so I will avoid repeating my previous points but from working on PouchDB,
the focus on having 'PouchDB' be a database only is fairly liberating, by
not trying
to add fairly arbitrary "application platform" features into t
Started with
python dev/run -n 1 --with-admin-party-please &
and export COUCH_HOST='http://127.0.0.1:15984'
On 12 October 2015 at 13:26, Jan Lehnardt wrote:
>
> > On 12 Oct 2015, at 13:15, Dale Harvey wrote:
> >
> >> - instead of fixed test db names
> - instead of fixed test db names like `test_suite_db` that are used in
almost every test,
> we now generate a random database name for each test. The JS tests
expected db
> deletion to be synchronous, and that’s no longer the case in 2.0. Instead
of
> error-prone polling to wait for db deletion,
Speaking from not a part of nano, but pouchdb has similiar checks and
requirements.
I just wanted to clarify, are you speaking about removing as a "pre-commit
hook", or removing the requirements for those checks to pass before merging?
The checks and tests existing and being enforced looks like a
And if anyone wants to make a start on travis
https://github.com/pouchdb/pouchdb/blob/master/.travis.yml and
https://github.com/pouchdb/pouchdb/blob/master/bin/run-couch-master-on-travis.sh
Should get you most of the way there
On 10 September 2015 at 11:40, Dale Harvey wrote:
> I dont th
I dont think CI is a dream, It should take an afternoon at most to get
CouchDB setup on travis on a single platform to ensure no major regressions
come though. If anyone wants help doing that feel free to ping me on
#pouchdb / #couchdb, we already test couchdb master in travis.
I do think multirep
[
https://issues.apache.org/jira/browse/COUCHDB-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395739#comment-14395739
]
Dale Harvey commented on COUCHDB-2237:
--
Also forgot to say thanks loads
[
https://issues.apache.org/jira/browse/COUCHDB-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395738#comment-14395738
]
Dale Harvey commented on COUCHDB-2237:
--
I wouldnt suggest any breaking changes
[
https://issues.apache.org/jira/browse/COUCHDB-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201822#comment-14201822
]
Dale Harvey commented on COUCHDB-2444:
--
Authentication from wildcard origins
[
https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Harvey closed COUCHDB-2205.
Resolution: Cannot Reproduce
Havent seen this in a while, didnt mean to edit the title, closing
[
https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Harvey updated COUCHDB-2205:
-
Description:
During the PouchDB test suite run I am seeing an intermittent 400
Dale Harvey created COUCHDB-2442:
Summary: Ability to ensure a cluster has been started successfully
Key: COUCHDB-2442
URL: https://issues.apache.org/jira/browse/COUCHDB-2442
Project: CouchDB
[
https://issues.apache.org/jira/browse/COUCHDB-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170871#comment-14170871
]
Dale Harvey commented on COUCHDB-2386:
--
Apparently there was a bug in the Cou
Dale Harvey created COUCHDB-2386:
Summary: Cant undelete documents in master
Key: COUCHDB-2386
URL: https://issues.apache.org/jira/browse/COUCHDB-2386
Project: CouchDB
Issue Type: Bug
I have a year old patch where I made a start on doing fuzzy replication
testing, I think CouchDB provides a super simple mechanism for property
testing since a really simple property is "after a bunch of stuff happens,
replicate between 2 databases and they should be the same"
https://github.com/p
Dale Harvey created COUCHDB-2383:
Summary: Installation instructions are wrong
Key: COUCHDB-2383
URL: https://issues.apache.org/jira/browse/COUCHDB-2383
Project: CouchDB
Issue Type: Bug
On 24 September 2014 15:12, Jan Lehnardt wrote:
>
> On 24 Sep 2014, at 13:26 , Alexander Shorin wrote:
>
> > Hi Jan,
> >
> > Looks good, replied inline.
> >
> > On Wed, Sep 24, 2014 at 2:35 PM, Jan Lehnardt wrote:
> >> # Setting up CouchDB 2.0
> >>
> >> Hey all, since we are getting close to fe
Dale Harvey created COUCHDB-2237:
Summary: Add a 'live' sugar for 'continuous'
Key: COUCHDB-2237
URL: https://issues.apache.org/jira/browse/COUCHDB-2237
Project: CouchDB
[
https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944135#comment-13944135
]
Dale Harvey commented on COUCHDB-2205:
--
Worth mentioning I hadnt ever previo
[
https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944097#comment-13944097
]
Dale Harvey commented on COUCHDB-2205:
--
The link from the gist never fired a
[
https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944096#comment-13944096
]
Dale Harvey commented on COUCHDB-2205:
--
I didnt see any 400 response at all in
[
https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943892#comment-13943892
]
Dale Harvey commented on COUCHDB-2205:
--
For some extra information about wha
[
https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943890#comment-13943890
]
Dale Harvey commented on COUCHDB-2205:
--
Here is a failing test with the Cou
Dale Harvey created COUCHDB-2205:
Summary: 400 bad_request on DELETE /db/
Key: COUCHDB-2205
URL: https://issues.apache.org/jira/browse/COUCHDB-2205
Project: CouchDB
Issue Type: Bug
I fully agree, its something I mentioned at the couchdb conf in vancouver,
a review first system encourages contributions and has multiple benefits
* At least 2 people look at the code, less likely to push silly mistakes
* Can codify and practice review rules
* Its much easier to view the curre
[
https://issues.apache.org/jira/browse/COUCHDB-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843730#comment-13843730
]
Dale Harvey commented on COUCHDB-1950:
--
So the problem being that in a sy
[
https://issues.apache.org/jira/browse/COUCHDB-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843170#comment-13843170
]
Dale Harvey commented on COUCHDB-1950:
--
Sorry I meant 'prune'
A d
[
https://issues.apache.org/jira/browse/COUCHDB-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843162#comment-13843162
]
Dale Harvey commented on COUCHDB-1950:
--
The notion that conflicts should no
[
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843121#comment-13843121
]
Dale Harvey commented on COUCHDB-1934:
--
+1
> jquery.couch
"Document foo/bar config option"
On 4 December 2013 16:54, Alexander Shorin wrote:
> On other hand when you see commit message:
>
> Add foo/bar config option
>
> What is your first though? Oh, new config option! But no, that was
> missed option description in docs. To resolve such collision I m
Also a reasonably weak -1, atomic updates to tests / docs / code is a good
thing, the tags are pretty much always inconsistent, they arent actually
useful for anything and additional steps are just another barrier
I have been asking people to avoid it on any codebases I review for
On 4 December
[
https://issues.apache.org/jira/browse/COUCHDB-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837480#comment-13837480
]
Dale Harvey commented on COUCHDB-1950:
--
This is something that can ha
[
https://issues.apache.org/jira/browse/COUCHDB-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837093#comment-13837093
]
Dale Harvey commented on COUCHDB-1948:
--
Likely worth mentioning that conflict
[
https://issues.apache.org/jira/browse/COUCHDB-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837071#comment-13837071
]
Dale Harvey commented on COUCHDB-1948:
--
It wont always generate a conflict,
So funnily enough I just got an email that couchapp.net which I had
registered was in its redemption period, I just renewed it and anyone is
free to it
On 2 December 2013 14:16, Noah Slater wrote:
> Thanks Benoit.
>
> If J Chris does not want to cede control of the domain, we might want
> to co
[
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834845#comment-13834845
]
Dale Harvey commented on COUCHDB-1934:
--
Although I dont love it, I do think
[
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834741#comment-13834741
]
Dale Harvey commented on COUCHDB-1934:
--
Yeh a console.warn in the fil
[
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834713#comment-13834713
]
Dale Harvey commented on COUCHDB-1934:
--
Having jquery.couch.js's
Sorry for taking a while to look at this, busy with couchdb conf etc
In general I agree with Jens, this serves as great documentation for how
CouchDB's replication works, but its very detailed without a high level
overview
The PouchDB replicator was done following what Jens documented @
https://g
about the implications / api and coming up
with a plugin plan I think is useful
On 29 July 2013 18:01, Jan Lehnardt wrote:
>
> On Jul 29, 2013, at 18:29 , Jason Smith wrote:
>
> >
> > On Mon, Jul 29, 2013 at 11:24 PM, Dirkjan Ochtman
> wrote:
> >> On Mo
On the topic of browser_id support in CouchDB, it feels like this is a big
chance to push for usable plugins, should the aim for this not to be
included into core but to be available as a one click install from
futon/fauxton (this and geocouch seem prime candidates)?
This isnt because I dont want
[
https://issues.apache.org/jira/browse/COUCHDB-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720726#comment-13720726
]
Dale Harvey commented on COUCHDB-1863:
--
Or somewhat more appropriate, the lin
[
https://issues.apache.org/jira/browse/COUCHDB-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720724#comment-13720724
]
Dale Harvey commented on COUCHDB-1863:
--
So something needs to go to make space
[
https://issues.apache.org/jira/browse/COUCHDB-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Harvey updated COUCHDB-1863:
-
Component/s: Website
> Documentation link should be on top links of front p
Dale Harvey created COUCHDB-1863:
Summary: Documentation link should be on top links of front page
Key: COUCHDB-1863
URL: https://issues.apache.org/jira/browse/COUCHDB-1863
Project: CouchDB
[
https://issues.apache.org/jira/browse/COUCHDB-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720707#comment-13720707
]
Dale Harvey commented on COUCHDB-1862:
--
In my head we want to allow 3 def
Dale Harvey created COUCHDB-1862:
Summary: Configuring CORS sucks
Key: COUCHDB-1862
URL: https://issues.apache.org/jira/browse/COUCHDB-1862
Project: CouchDB
Issue Type: Bug
+1000, thanks for this Jan
It very much models both I how I think about CouchDB and how I think +
architect PouchDB (much of that is echoed on http://pouchdb.com/)
I have quite a lot of thoughts on this, most of them technical so I will do
them in seperate threads, but wanted to voice my agreemen
For Pouch we have spent a lot of time rewriting a lot of the couch tests to
be suitable for testing Pouch, we have put a pretty huge effort into
testing and although our current suite isnt a suitable replacement for the
couch suite, if it was possible I would definitely love to work on a single
sui
at 16:49, Wendall Cada wrote:
> >
> > > Welcome Dale! Congrats. :)
> > >
> > > On 04/29/2013 06:52 AM, Noah Slater wrote:
> > > > Dear community,
> > > >
> > > > I am pleased to announce that the CouchDB Project Management
> C
ompatible and extended support / backports are for backporting bugfixes to
major version
changes, the release procedure is a slow process and it seems like having 4
active versions
is also confusing for users, but my experience may be differing
requirements.
> > On 25 April 2013 22:03, Da
#1 is the procedure almost every project I have worked on follows, we do
actually have an integration branch at mozilla but that is purely due to
the sheer size of the codebase and volume of changes, I see no reason why
CouchDB shouldnt be permanently releasable or why a release would be
'ongoing',
We have been looking to reuse the CouchDB javascript tests for PouchDB and
extracted them into a seperate npm package
https://npmjs.org/package/couchdb-harness
The idea was that we could reused the same test suite and throw ours away
however it hit a few problems, mostly that the test suite requi
+1
==
apache-couchdb-1.3.0 archives ready for distribution:
apache-couchdb-1.3.0.tar.gz
==
woot,
OSX 10.7.5
Erlang R15B01
SpiderMonkey 1.8.5
On 2 April 2013 13:21, Jan Lehnardt wrote:
> *p
Dale Harvey created COUCHDB-1678:
Summary: Seach in the documentation 404's
Key: COUCHDB-1678
URL: https://issues.apache.org/jira/browse/COUCHDB-1678
Project: CouchDB
Issue Type
[
https://issues.apache.org/jira/browse/COUCHDB-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499581#comment-13499581
]
Dale Harvey commented on COUCHDB-1607:
--
Good debugging, you can use re:s
[
https://issues.apache.org/jira/browse/COUCHDB-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491287#comment-13491287
]
Dale Harvey commented on COUCHDB-431:
-
Oh and one last comment, and the only o
[
https://issues.apache.org/jira/browse/COUCHDB-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490747#comment-13490747
]
Dale Harvey commented on COUCHDB-431:
-
Cheers for this benoitc
Off the la
Benoit
This problem has nothing to do with any application, its a bug in CouchDB
with a simple fix
On 4 November 2012 20:43, Benoit Chesneau (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/COUCHDB-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focuse
I havent had a chance yet but will definitely testing it out tomorrow
On 3 November 2012 11:35, Robert Newson wrote:
> Haven't had a chance yet, let's not merge until a review or two
>
>
> On 3 November 2012 18:15, Benoit Chesneau wrote:
>
> > bump.
> >
> > Anyone tried it ? Is a merge in mast
Awesome that this is kicking off proper again, So one thing I meant to
bring up earlier, but being in this thread scares me :)
One really great feature that would need to be thought about and baked in
from very early on, is using futon to control multiple instances of
CouchDB, not just the CouchDB
This is awesome, thanks benoitc (and sorry for dropping the ball on this)
Will test it out and get back to you
On 31 October 2012 23:52, Benoit Chesneau wrote:
> Hello all,
>
> So I finally committed my patch about CORS support following the current
> W3C working draft [1]. This patch support
tory structure into doc attachments? That's a
> > different tool to something that assembles a design doc from a directory,
> > right?
> >
> > On Wed, Sep 26, 2012 at 10:11 AM, Simon Metson
> wrote:
> >
> > > Hi
> > >
> > >
> &g
jango project. In fact, for any system that uses the filesystem as
> state, it is fairly common to have structure. And as Benoit pointed out
> before, CouchApps are more than just uploading some HTML into CouchDB.
>
> On Wed, Sep 26, 2012 at 9:49 AM, Dale Harvey wrote:
>
> >
I have a folder here with an index.html file in it
Can I upload it to CouchDB as an attachment without moving it? last time
remember (admittedly a long time ago) I couldnt do that with erica nor the
couchapppy tool
If not, I think that is one of the primary use cases that should be kept in
mind,
On 25 September 2012 14:39, Benoit Chesneau wrote:
> On Tue, Sep 25, 2012 at 3:29 PM, Dale Harvey wrote:
> > Just wanted to chime in on a few points
> >
> > I think Couch should definitely ship with a tool to upload a design doc,
> I
> > think we pretty much all
Just wanted to chime in on a few points
I think Couch should definitely ship with a tool to upload a design doc, I
think we pretty much all agreed on that in Boston, its not even particular
to couchapps but a fairly basic requirement for anyone that has to manage
their map reduce code.
I do have
Rather a lot of the CouchDB Community will be attending
http://2012.lxjs.org/
Seems like it would be a decent idea to organise something for just before
that?
On 31 August 2012 13:17, Benoit Chesneau wrote:
> On Fri, Aug 31, 2012 at 5:05 PM, Simon Metson wrote:
> > I think (Dave/Joan/Bob can c
Dale Harvey created COUCHDB-1487:
Summary: If-None-Match isnt invalidated by Accept type
Key: COUCHDB-1487
URL: https://issues.apache.org/jira/browse/COUCHDB-1487
Project: CouchDB
Issue Type
> the filter, or not, thus bypassing it.
>
> Cheers
> Jan
> --
>
> >
> > On Tue, Mar 13, 2012 at 08:33, Dale Harvey wrote:
> >
> >> On 13 March 2012 15:30, Dale Harvey wrote:
> >>
> >>> So I was trying to implement the ability for
So I was trying to implement the ability for logged in users to subscribe
to the changes feed for updates to their own documents (its currently admin
only), its a simple patch but its not very clean (mostly because the we
dont want to have the changes feed read the full document)
A way that I coul
On 13 March 2012 15:30, Dale Harvey wrote:
> So I was trying to implement the ability for logged in users to subscribe
> to the changes feed for updates to their own documents (its currently admin
> only), its a simple patch but its not very clean (mostly because the we
> dont want
I will happily volunteer to work on generating html output from whatever we
store the documentation in, ultimately I think they should be integrated
into futon, and I would request that whatever the documentation is stored
in, that its its reasonably easy to parse and wrangle into your own output *
[
https://issues.apache.org/jira/browse/COUCHDB-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Harvey closed COUCHDB-1090.
Resolution: Won't Fix
I dont think its sensible to have jquery.couch drive futon and be
[
https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Harvey closed COUCHDB-912.
---
Resolution: Won't Fix
I dont think this is a particularly nice sol
I think this is a great idea
I am not one of the CouchDB devs, and wouldnt be able to give particularly
good insight into the inner workings of particular modules / features, but
I am pretty comfortable with erlang and developing inside the Couch
codebase, I would be happy to volunteer to help whe
Feel free to disregard this as irrelevant as I am pretty ignorant about the
history involved but I am interested in why spidermonkey is not packaged
inside of CouchDB as a few of the other dependancies are.
Every time I build Couch on a new machine linking against spidermonkey
breaks in some way,
[
https://issues.apache.org/jira/browse/COUCHDB-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107550#comment-13107550
]
Dale Harvey commented on COUCHDB-1286:
--
I tested the patch against 1.2.x on
[
https://issues.apache.org/jira/browse/COUCHDB-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107547#comment-13107547
]
Dale Harvey commented on COUCHDB-1286:
--
Thats quick work, I attached my nginx.
[
https://issues.apache.org/jira/browse/COUCHDB-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Harvey updated COUCHDB-1286:
-
Attachment: nginx.conf
> Cannot replicate with nginx as reverse pr
[
https://issues.apache.org/jira/browse/COUCHDB-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Harvey updated COUCHDB-1286:
-
Attachment: repl.log
> Cannot replicate with nginx as reverse pr
Affects Versions: 1.2
Reporter: Dale Harvey
Replicating between 2 CouchDB instances on 1.2.x branch, one sites behind
nginx, a push replication to the one behind nginx fails with the attached log
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http
On 17 August 2011 02:47, Adam Kocoloski wrote:
> On Aug 16, 2011, at 8:20 PM, Randall Leeds wrote:
>
> > On Tue, Aug 16, 2011 at 17:03, Adam Kocoloski
> wrote:
> >
> >> On Aug 16, 2011, at 5:46 PM, Randall Leeds wrote:
> >>
> >>> -1 on _skip_validation and new role
> >>>
> >>> One can always wri
> I heard different but that's good news. Getting 1.0.3 out is a good
> thing, this thread has gone cold.
Yeh sorry this was my bad, I was testing against trunk and made a wrong
assumption about when the data_size patch that breaks compatibility was
introduced
On 13 July 2011 13:36, kowsik wrote
On 21 June 2011 17:05, Noah Slater wrote:
>
> On 21 Jun 2011, at 16:46, Dale Harvey wrote:
>
> > + src
> > + ebin
> > + couch.app
> > + lib
> > + ejson
> > + src
> > + ibrowse
> > + src
>
> Too much root director
In the interest of keeping small changes, I would have thought it would be
very easy to do a renaming of the source level directory layout to as
proposed (I have no strong opinion on rel/ priv/ etc)
+ src
+ ebin
+ couch.app
+ lib
+ ejson
+ src
+ ibrowse
+ src
and keep the build t
[
https://issues.apache.org/jira/browse/COUCHDB-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Harvey updated COUCHDB-1180:
-
Attachment: deferreds.patch
> Add deferred support to jquery.couch
Reporter: Dale Harvey
Priority: Minor
the recent releases of jquery have included deferreds which are an improved api
for handling asynchronous callbacks, it is backwards compatible with the
current use and just requires access to to the currently unused returned values
from
[
https://issues.apache.org/jira/browse/COUCHDB-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031662#comment-13031662
]
Dale Harvey commented on COUCHDB-1158:
--
Awesome Filipe, confirmed that fixe
Issue Type: Bug
Components: Database Core
Environment: OSX, Built from Git - 1.2.0a8a37632-git
Reporter: Dale Harvey
When a document contains a simple unicode escaped character and the log level
is set to debug, running any view over the document crashes the log
[
https://issues.apache.org/jira/browse/COUCHDB-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031480#comment-13031480
]
Dale Harvey commented on COUCHDB-1156:
--
A screenshot of the issue
1 - 100 of 156 matches
Mail list logo
