On 2020-06-24 1:32 p.m., Garren Smith wrote:
On Wed, Jun 24, 2020 at 6:47 PM Joan Touzet wrote:
Hi Garren,
If the "options" field is left out, what is the default behaviour?
All group_levels will be indexed. I imagine this is what most CouchDB uses
will want.
Great!
Is there no
On Wed, Jun 24, 2020 at 6:47 PM Joan Touzet wrote:
> Hi Garren,
>
> If the "options" field is left out, what is the default behaviour?
>
All group_levels will be indexed. I imagine this is what most CouchDB uses
will want.
> Is there no way to specify multiple group_levels to get results that
Hi Garren,
If the "options" field is left out, what is the default behaviour?
Is there no way to specify multiple group_levels to get results that
match the original CouchDB behaviour? Your changed behaviour would be
acceptable if I could do something like `?group_level=2,3,4,5`.
-Joan
On
Hi Jan,
Thanks, one of my first attempts https://github.com/garrensmith/fortuna was
embedding v8 as a nif. It was my first nif and the implementation is wrong,
but it did prove it was possible and something we could consider going
forward. The one thing I'm not 100% sure of is moving V8 across
Congrats Garren, this is really cool! :)
One related question: have you pondered embedding a JS engine into Erlang
itself as well?
Best
Jan
—
> On 24. Jun 2020, at 16:21, Garren Smith wrote:
>
> Hi All,
>
> I've been playing around with the rust language quite a bit recently and
> using it
Wow that's very cool man, I'll read it and share it with my fellow
rustaceans!
On Wed, Jun 24, 2020 at 4:21 PM Garren Smith wrote:
> Hi All,
>
> I've been playing around with the rust language quite a bit recently and
> using it to write some rust related side projects. I've recently finished a
Hi All,
I've been playing around with the rust language quite a bit recently and
using it to write some rust related side projects. I've recently finished a
CouchDB View Server written in Rust using V8. Here is a blog post about
that details the new View Server protocol for CouchDB 4.x and my
Hi,
I share the discomfort in fauxton making a remote connection without warning
and agree with Jan that some confirmation screen should be added.
It's also fine for this to be on master while it develops, master is not a
release and is not guaranteed to be releasable either. Anyone deploying
> On 24. Jun 2020, at 14:31, ermouth wrote:
>
>> My PR was meant to start this discussion
>
> Unfortunately it was instead merged to master, which is unbearable imho.
> Shouldn’t that PR be rolled back and removed from the master branch
> immediately then?
as long as we make sure we don’t
> My PR was meant to start this discussion
Unfortunately it was instead merged to master, which is unbearable imho.
Shouldn’t that PR be rolled back and removed from the master branch
immediately then?
As a proposal it’s ok, but to achieve intended goal I think it’s enough to
add blogs to
Quick Note I have a gist markdown version of this that might be easier to
read https://gist.github.com/garrensmith/1ad1176e007af9c389301b1b6b00f180
Hi Everyone,
The team at Cloudant have been relooking at Reduce indexes for CouchDB on
FDB and we want to simply what we had initially planned and
Thanks ermouth,
I’m surprised my proposal made it through without discussion. I have the
same question ;D
FWIW, this “leaks” the browser connection to the internet, not necessarily
CouchDB instance data.
For a production version of this, I would at least expect an opt-in button
on that page,
Since I hadn’t received any answer at Github, I’d like to raise an
important CouchDB Fauxton security question publicly.
One of the latest Fauxton PRs (
https://github.com/apache/couchdb-fauxton/pull/1284) adds a remote newsfeed
to Fauxton. Emitting a newsfeed in the admin panel in that way may
13 matches
Mail list logo