On Wed, Jan 27, 2010 at 11:18 PM, Dirkjan Ochtman wrote:
> On Thu, Jan 28, 2010 at 01:06, Chris Anderson wrote:
>> Is anyone else having trouble with views that emit Date objects in the
>> key (running latest trunk)?
>
> From memory, I wonder if emitting Date objects for
> JSON.stringification is
On Thu, Jan 28, 2010 at 01:06, Chris Anderson wrote:
> Is anyone else having trouble with views that emit Date objects in the
> key (running latest trunk)?
>From memory, I wonder if emitting Date objects for
JSON.stringification is valid according to the spec. I remember that
the Firefox JSON imp
[
https://issues.apache.org/jira/browse/COUCHDB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damjan Georgievski updated COUCHDB-321:
---
Attachment: futon-proxy-fix.diff
attaching the fix.
ps. the nginx conf used for tes
[
https://issues.apache.org/jira/browse/COUCHDB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805767#action_12805767
]
Damjan Georgievski commented on COUCHDB-321:
In my opinion it would be better
>
> $ js -v
> JavaScript-C 1.8.0 pre-release 1 2007-10-03
>
$ js -v
JavaScript-C 1.7.0 2007-10-03
And I have the same on both servers which I was testing from. The
working one (0.11.0b898401) and the weird one (0.11.0b903617)
--
Slan,
David
On Wed, Jan 27, 2010 at 5:37 PM, David Coallier
wrote:
>>
>> I just tested with my copy of trunk and this temp view:
>>
>> function(doc) {
>> var d = new Date("2010/02/04");
>> emit(d, null);
>> }
>>
>> I only have one doc, in there, so my rows are
>>
>> "2010-02-04T08:00:00.000Z", null
>>
>> Wh
> I should ask, to make sure I'm not crazy:
>
> Is anyone else having trouble with views that emit Date objects in the
> key (running latest trunk)?
>
> How do we feel about the new undefined handling? It should be worth it
> in terms of compatibility with other engines.
>
> Everything works for me
>
> I just tested with my copy of trunk and this temp view:
>
> function(doc) {
> var d = new Date("2010/02/04");
> emit(d, null);
> }
>
> I only have one doc, in there, so my rows are
>
> "2010-02-04T08:00:00.000Z", null
>
> Which to me looks like what I was expecting.
>
I have tried on a clean
On Wed, Jan 27, 2010 at 3:52 PM, Chris Anderson wrote:
> On Wed, Jan 27, 2010 at 12:41 PM, David Coallier
> wrote:
>>> Can you try with r902422?
>>>
>
> I just tested with my copy of trunk and this temp view:
>
> function(doc) {
> var d = new Date("2010/02/04");
> emit(d, null);
> }
>
> I only
On Wed, Jan 27, 2010 at 12:41 PM, David Coallier
wrote:
>> Can you try with r902422?
>>
I just tested with my copy of trunk and this temp view:
function(doc) {
var d = new Date("2010/02/04");
emit(d, null);
}
I only have one doc, in there, so my rows are
"2010-02-04T08:00:00.000Z", null
W
> Can you try with r902422?
>
> If this is a consequence of the json2.js change, we'll have to fix it.
I believe this is a consequence of json2.js as well (At least that's
the only difference that deals with time related matter that I could
identify).
In fact how I fixed my code for now since th
On Wed, Jan 27, 2010 at 10:21 AM, David Coallier
wrote:
> Hey lads,
>
> I'm suspecting a bug but before I report I was wondering if anyone was
> aware of a change that would have happened between 0.11.0b898401 and
> 0.11.0b903617.
Can you try with r902422?
If this is a consequence of the json2.j
Cool, cool! I'll take a look!
On Wed, Jan 27, 2010 at 00:34, Filipe David Manana wrote:
> Randall,
>
> I submitted a patch for it 1 or 2 days ago:
> https://issues.apache.org/jira/browse/COUCHDB-631
> (not reviewed yet I think)
>
>
> On Tue, Jan 26, 2010 at 7:07 PM, Randall Leeds >wrote:
>
> > O
On Wed, Jan 27, 2010 at 5:26 PM, Chris Anderson wrote:
> On Wed, Jan 27, 2010 at 8:12 AM, Jan Lehnardt wrote:
>>
>> On 27 Jan 2010, at 07:27, Brian Candler wrote:
>>
>>> On Wed, Jan 27, 2010 at 06:33:12AM -0800, Jan Lehnardt wrote:
I'm not a crypto expert, but it seems we can get away with s
On Wed, Jan 27, 2010 at 08:26:39AM -0800, Chris Anderson wrote:
> > My reasoning here is that a SHA implementation is easier to come by
> > universally
> > than a bcrypt one.
>
> More secure without more dependencies," which works for me.
SHA1 != HMAC_SHA1
If you want a format that doesn't tie
On Wed, Jan 27, 2010 at 08:12:28AM -0800, Jan Lehnardt wrote:
> Quoting http://en.wikipedia.org/wiki/HMAC:
>
> "The values of ipad and opad are not critical to the security of the
> algorithm"
>
> If you mean these by "secret", otherwise I don't follow.
*The* secret. HMAC is a function with
Hey lads,
I'm suspecting a bug but before I report I was wondering if anyone was
aware of a change that would have happened between 0.11.0b898401 and
0.11.0b903617.
The problem is quite simple, I have a few on 0.11.0b898401 that pretty
much does that:
function(doc) {
var x = new Date(126451533
[
https://issues.apache.org/jira/browse/COUCHDB-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana updated COUCHDB-583:
--
Attachment: couchdb-583-trunk-16th-try-git.patch
So, here it follows the correction.
Now usin
Chris Anderson wrote:
> Awesome, a CouchDB emulator for MongoDB in 300 lines of Ruby:
>
> http://github.com/sbellity/futon4mongo/blob/master/serve
That's indeed pretty cool - can we leverage Benoits rewrite handler to
do it the other way round?
regards,
Joscha
--
[
https://issues.apache.org/jira/browse/COUCHDB-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805569#action_12805569
]
Filipe Manana commented on COUCHDB-631:
---
Ah!
I was not aware that only the latest r
[
https://issues.apache.org/jira/browse/COUCHDB-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805566#action_12805566
]
Chris Anderson commented on COUCHDB-631:
There's a better approach:
Instead of fo
[
https://issues.apache.org/jira/browse/COUCHDB-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Anderson reassigned COUCHDB-631:
--
Assignee: Chris Anderson
> Replication by doc Ids
> --
>
>
On Wed, Jan 27, 2010 at 8:32 AM, Simon Metson
wrote:
> Hi,
>
> On 27 Jan 2010, at 16:22, Chris Anderson wrote:
>
>> On Wed, Jan 27, 2010 at 3:09 AM, Simon Metson
>> wrote:
>>>
>>> There's a MongoDB Futon clone...
>>>
>>
>> There's Booth -- it's a ruby in-memory couch that runs Futon.
>>
>> http:/
Hi,
On 27 Jan 2010, at 16:22, Chris Anderson wrote:
On Wed, Jan 27, 2010 at 3:09 AM, Simon Metson
wrote:
There's a MongoDB Futon clone...
There's Booth -- it's a ruby in-memory couch that runs Futon.
http://github.com/jchris/booth
I was thinking of http://github.com/sbellity/futon4mongo
On Wed, Jan 27, 2010 at 8:12 AM, Jan Lehnardt wrote:
>
> On 27 Jan 2010, at 07:27, Brian Candler wrote:
>
>> On Wed, Jan 27, 2010 at 06:33:12AM -0800, Jan Lehnardt wrote:
>>> I'm not a crypto expert, but it seems we can get away with sha1 if we use
>>> HMAC instead of just hashing + salting:
>>
>>
On Wed, Jan 27, 2010 at 3:09 AM, Simon Metson
wrote:
> There's a MongoDB Futon clone...
>
There's Booth -- it's a ruby in-memory couch that runs Futon.
http://github.com/jchris/booth
> On 27 Jan 2010, at 08:41, Joscha Feth wrote:
>
>> Jan Lehnardt wrote:
>>
>>> How is this relevant to the dev
On 27 Jan 2010, at 07:27, Brian Candler wrote:
> On Wed, Jan 27, 2010 at 06:33:12AM -0800, Jan Lehnardt wrote:
>> I'm not a crypto expert, but it seems we can get away with sha1 if we use
>> HMAC instead of just hashing + salting:
>
> Errm, do you mean HMAC with a fixed server-side secret?
>
>
s/vbuilds/vpath builds/
I obviously need another cup...
On Wed, Jan 27, 2010 at 10:34 AM, Paul Joseph Davis (JIRA)
wrote:
>
> [
> https://issues.apache.org/jira/browse/COUCHDB-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805539#action_12805539
[
https://issues.apache.org/jira/browse/COUCHDB-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805539#action_12805539
]
Paul Joseph Davis commented on COUCHDB-583:
---
@Filipe,
Actually you want to use
On Wed, Jan 27, 2010 at 06:33:12AM -0800, Jan Lehnardt wrote:
> I'm not a crypto expert, but it seems we can get away with sha1 if we use
> HMAC instead of just hashing + salting:
Errm, do you mean HMAC with a fixed server-side secret?
This means that if you replicate user records between servers
[
https://issues.apache.org/jira/browse/COUCHDB-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805533#action_12805533
]
Filipe Manana commented on COUCHDB-583:
---
Yep,
I should have used
{ok, Data} =
fi
[
https://issues.apache.org/jira/browse/COUCHDB-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805526#action_12805526
]
Paul Joseph Davis commented on COUCHDB-583:
---
s/directory permissions/file paths/
[
https://issues.apache.org/jira/browse/COUCHDB-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805518#action_12805518
]
Paul Joseph Davis commented on COUCHDB-583:
---
It was probably the directory permi
On 25 Jan 2010, at 21:02, Chris Anderson wrote:
> On Tue, Jan 5, 2010 at 10:21 PM, Benoit Chesneau wrote:
>>> --
>> There is a blowfish encryption implementation available in javascript.
>> doesn't bcrypt stand for "blowfish crypt" ?
>> http://www.openbsd.org/cgi-bin/man.cgi?query=bcrypt&apropo
On 25 Jan 2010, at 16:48, Noah Slater wrote:
> Score 1 for team Noah.
*wiggles pom-poms*
> On 26 Jan 2010, at 00:42, Paul Davis wrote:
>
>> Looks like you forgot to add json2.js to license.skip
>>
>> On Mon, Jan 25, 2010 at 7:57 PM, wrote:
>>> The Buildbot has detected a new failure of cou
On 25 Jan 2010, at 10:37, Chris Anderson wrote:
> On Mon, Jan 25, 2010 at 8:28 AM, Zachary Zolton
> wrote:
>> Having the replicator handle chaining views would really help people
>> who are already hacking this together with scripts. So, I'd definitely
>> +1 the idea. Isn't view size and indexin
Hey Chris,
The main issue here is how good your view server is; can it take
getting
1000's of responses at once? An HTTP view response would be nice...
I'm
pretty sure that CouchDB could handle getting all the requests from
workers.
I think this could also allow for view of view processing,
There's a MongoDB Futon clone...
On 27 Jan 2010, at 08:41, Joscha Feth wrote:
Jan Lehnardt wrote:
How is this relevant to the development of CouchDB?
I think he wants to show us how glad we can be to have futon :-D
regards,
Joscha
--
[
https://issues.apache.org/jira/browse/COUCHDB-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805468#action_12805468
]
Filipe Manana commented on COUCHDB-583:
---
@Chris
just a quick thought. You invoked t
Jan Lehnardt wrote:
> How is this relevant to the development of CouchDB?
I think he wants to show us how glad we can be to have futon :-D
regards,
Joscha
--
Randall,
I submitted a patch for it 1 or 2 days ago:
https://issues.apache.org/jira/browse/COUCHDB-631
(not reviewed yet I think)
On Tue, Jan 26, 2010 at 7:07 PM, Randall Leeds wrote:
> On Sun, Jan 24, 2010 at 00:09, Chris Anderson wrote:
>
> > Devs,
> >
> > I've been thinking there are a few
[
https://issues.apache.org/jira/browse/COUCHDB-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805410#action_12805410
]
Filipe Manana commented on COUCHDB-583:
---
@Chris,
thanks for looking at it :)
That'
42 matches
Mail list logo
