Re: View keys case-insensitive?

2009-04-10 Thread Patrick Antivackis
Your welcome, for one time I can help you and not the opposite 2009/4/10 Paul Davis > > (let's say we use Level 3) > > sortKey=[]; > > for (i=0; i<3; i++) { > > for(j=0; j >sortKey.push(sArray[j][i]); > > } > > > > } > > Patrick! A million thanks. Seeing this in code I at first thought,

Re: View keys case-insensitive?

2009-04-10 Thread Patrick Antivackis
ting this) then when I compare a and A, A > a. I don't see why > any other character is considered. A is fucking bigger than a. If > there is a section that says, "Oh, btw, if one string is an exact > prefix of the other as defined solely by primary weights, then the > pre

Re: View keys case-insensitive?

2009-04-09 Thread Patrick Antivackis
> http://unicode.org/reports/tr10/ > > I feel like printing the entire thing just so I can have a book burning. > > On Thu, Apr 9, 2009 at 6:39 PM, Patrick Antivackis > wrote: > > By the way, what customization did you try to send to ICU ? > > > > 2009/4/10 Paul

Re: View keys case-insensitive?

2009-04-09 Thread Patrick Antivackis
hat 'A; > should come after 'a' I still can't get the expected "a < aa < A" > behavior. In a nutshell, "Why the hell does the second 'a' alter the > comparison?" > > HTH, > Paul Davis > > On Thu, Apr 9, 2009 at 5:45 PM,

Re: View keys case-insensitive?

2009-04-09 Thread Patrick Antivackis
in fact 7 letters ;) So collation is about comparing words together and if a word as less letter than an other it is placed first. Hope that helps 2009/4/10 Patrick Antivackis > As i said, ICU is more about language. > If you open your dictionnary you will find big before biggest (wh

Re: View keys case-insensitive?

2009-04-09 Thread Patrick Antivackis
'A; > should come after 'a' I still can't get the expected "a < aa < A" > behavior. In a nutshell, "Why the hell does the second 'a' alter the > comparison?" > > HTH, > Paul Davis > > On Thu, Apr 9, 2009 at 5:45 PM, Patri

Re: View keys case-insensitive?

2009-04-09 Thread Patrick Antivackis
It's quite normal as far as ICU is concerned. ICU is about language not about ASCII code. In ICU, case is the third element looked for comparison (same level than circled letter in Nordic languages for example), so not very important. So when you sort words together, a or A is still an a, so they a

Re: Introducing CouchDB Ltd.

2009-03-08 Thread Patrick Antivackis
> > After Anthony's email, I'm starting to feel my opinion shift. > It's Patrick ;) > However, I think this would only apply if Apache held rights to the name. > Thats' why it's better to ask legals from ASF

Re: Introducing CouchDB Ltd.

2009-03-08 Thread Patrick Antivackis
Hi Jan, Great news, I hope you lot of success > I'm sorry, but I'm going to have to disagree with you here. > > It's not unheard of for open source projects to evolve like this, see > WordPress. > > -- > Noah Slater, http://tumbolia.org/nslater > Sure Noah, but Wordpress is not as ASF project, t

Re: REST, Hypermedia, and CouchApps

2009-02-26 Thread Patrick Antivackis
OOops, click reply too fast there is already the include_design: true option in _design docs so why not add design_only : true option 2009/2/26 Patrick Antivackis > You got a point, > so OK may be need to add option in couchDB, but like this users could also > modify the view in ord

Re: REST, Hypermedia, and CouchApps

2009-02-26 Thread Patrick Antivackis
/2/26 Jan Lehnardt > > On 26 Feb 2009, at 12:57, Patrick Antivackis wrote: > > And ? >> Once it has runned once, it just takes into account the new docs >> > > So you are suggesting we add a view that needs to be updated > with potentially millions of documents

Re: REST, Hypermedia, and CouchApps

2009-02-26 Thread Patrick Antivackis
And ? Once it has runned once, it just takes into account the new docs 2009/2/26 Jan Lehnardt > > On 26 Feb 2009, at 12:42, Patrick Antivackis wrote: > > >>> That would certainly lower the number of require requests. I thought >>> for a minute about using a temp_

Re: REST, Hypermedia, and CouchApps

2009-02-26 Thread Patrick Antivackis
> > That would certainly lower the number of require requests. I thought > for a minute about using a temp_view for this, but there is no way to > restrict them to run on only the design docs, so the overhead could be > tremendous. I still think it'd be trivial to implement as part of a > view-like

Re: REST, Hypermedia, and CouchApps

2009-02-25 Thread Patrick Antivackis
2009/2/25 Patrick Antivackis > I think I'm in favor of doing it the longer way. It's more consistent. It >> will break stuff every client library that uses views, but each will be easy >> to fix. >> >> -Damien >> > > Else it could be good to

Re: REST, Hypermedia, and CouchApps

2009-02-25 Thread Patrick Antivackis
> > I think I'm in favor of doing it the longer way. It's more consistent. It > will break stuff every client library that uses views, but each will be easy > to fix. > > -Damien > Else it could be good to set the Content-Location header, but seems nobody except Opera respect the rfc

Re: REST, Hypermedia, and CouchApps

2009-02-25 Thread Patrick Antivackis
Very interesting Chris, Personnally, I not yet to use CouchApp nor _show nor _ list in a real projects, but i have played with in order to see how it's working. Also a a background i played also with sling ( http://incubator.apache.org/sling) that is (purist please it's just to simplify) a restful

Re: Fail on a simple case on replication

2009-02-24 Thread Patrick Antivackis
2009/2/24 Jan Lehnardt > > On 24 Feb 2009, at 13:52, Patrick Antivackis wrote: > >> It's like all politically correct terminology where you use a stupid >>>> expression in order to be as neutral as possible. >>>> >>>> >>> You ha

Re: Fail on a simple case on replication

2009-02-24 Thread Patrick Antivackis
Hi Jan, > > Oh and by the way, in a use case where there is only one database and you >> don't use compaction because you want to keep everything, well _rev is a >> revision that can be used to see the history of the document. >> > > You still shouldn't and that's what's in the documentation :)

Re: Fail on a simple case on replication

2009-02-24 Thread Patrick Antivackis
Oh and by the way, in a use case where there is only one database and you don't use compaction because you want to keep everything, well _rev is a revision that can be used to see the history of the document. I really don't see the point of renaming an attribute to make it harder to understand it's

Re: Fail on a simple case on replication

2009-02-23 Thread Patrick Antivackis
OK , upadated : http://wiki.apache.org/couchdb/Document_revisions Created : http://wiki.apache.org/couchdb/Replication (need more work) 2009/2/23 Jan Lehnardt > > On 23 Feb 2009, at 16:40, Patrick Antivackis wrote: > > May be i can start a wiki page on replication, but i think

Re: Fail on a simple case on replication

2009-02-23 Thread Patrick Antivackis
history. So for each document i'm able to do a revs=true, but I am unable to see the content of a previous version. May be i can start a wiki page on replication, but i think the http://couchdb.apache.org/docs/overview.html should be clarified too. 2009/2/23 Jan Lehnardt > > On

Re: Fail on a simple case on replication

2009-02-23 Thread Patrick Antivackis
For a reminder : revision (n) 1. the act or process of revising, 2. a corrected or new version of a book, article, etc. For me this term is correct with the use in Couch I think a good explanation of what a compaction/replication are doing (ie removing old rev, or replicating only current rev)

Re: Futon Future

2009-02-17 Thread Patrick Antivackis
gt; On 17 Feb 2009, at 13:45, Patrick Antivackis wrote: > > Hi Jan, >> I have quite good skills in Jquery and the way futon is using it. >> I think your proposal is promising, and should even go a step further with >> may be a specific CouchDB base dedicated to plugins. The in

Re: Futon Future

2009-02-17 Thread Patrick Antivackis
Hi Jan, I have quite good skills in Jquery and the way futon is using it. I think your proposal is promising, and should even go a step further with may be a specific CouchDB base dedicated to plugins. The installation of new plugin would then be easy. As jquery can charge and execute script on the

[jira] Commented: (COUCHDB-241) Add copy and move document in Futon

2009-02-11 Thread Patrick Antivackis (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672566#action_12672566 ] Patrick Antivackis commented on COUCHDB-241: This patch provides copy

Re: proposed replication rev history changes

2009-02-08 Thread Patrick Antivackis
e_seq in the replication record. Hope that helps, > > Adam > > > On Feb 8, 2009, at 3:11 PM, Patrick Antivackis wrote: > > Sorry Paul, but i thought Couch could do miracles. >> >> Adam, back to the _all_docs_by_seq view, if key of the myDoc is lower then >> t

Re: proposed replication rev history changes

2009-02-08 Thread Patrick Antivackis
n, Feb 8, 2009 at 1:48 PM, Adam Kocoloski > wrote: > > > > On Feb 8, 2009, at 1:38 PM, Patrick Antivackis wrote: > > > >> 3) > >> NodeA : > >> _id : myDoc _rev : 7-moe actual-rev-history [1-bart, 2-lisa, 3-homer, > >> 4-marge, 5-patty,

Re: proposed replication rev history changes

2009-02-08 Thread Patrick Antivackis
; Its possible I missed something that special casing the initial > revision would solve, but as I read the proposal it doesn't really fix > the underlying problem of possibly spurious conflicts while > introducing more complexity into the code. > > HTH, > Paul Davis > > On

Re: proposed replication rev history changes

2009-02-08 Thread Patrick Antivackis
And what today's revision system help in such a case ? 2009/2/8 Paul Davis > On Sun, Feb 8, 2009 at 11:50 AM, Patrick Antivackis > wrote: > > I'm not sure I understood what you asked. > > > > It would be a conflict of document, that would need either man

Re: proposed replication rev history changes

2009-02-08 Thread Patrick Antivackis
t the origin if replications occurs after you trimmed the reference to the first revision. 2009/2/8 Paul Davis > On Sun, Feb 8, 2009 at 6:07 AM, Patrick Antivackis > wrote: > > 2009/2/8 Damien Katz > > > >> You got everything right except this. It doesn't so

Re: couchdb transactions changes

2009-02-08 Thread Patrick Antivackis
Does Couch really has to be ACID compliant, lot of ACID databases exist already from traditional RDBMS to Java Content Repository (Document databases that are compliant to JSR 170 level 2) such as Jackrabbit from Apache or ExoJCR or Alfresco. And traditional databases has always been a pain in th

Re: proposed replication rev history changes

2009-02-08 Thread Patrick Antivackis
2009/2/8 Damien Katz > You got everything right except this. It doesn't solve the problem, because > on another node, I could have a document that looked like ["1-foo" "2-bif"]. > That is a real edit conflict that wouldn't be caught by what I think you are > proposing. > That's right, there is

Re: proposed replication rev history changes

2009-02-07 Thread Patrick Antivackis
Thank you for the preview. I will just think loud in order to comment your explaination. As for background how it's working today: version of a document : a version of a document is identified by an id and a revision. The version of the document contains all the fileds/values as they were at thi

[jira] Commented: (COUCHDB-128) couchdb is not starting properly from init.d script in trunk

2009-02-07 Thread Patrick Antivackis (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671440#action_12671440 ] Patrick Antivackis commented on COUCHDB-128: On my side there are two th

Re: Transactional _bulk_docs

2009-02-06 Thread Patrick Antivackis
Excuse me to interfere in this fascinating thread, but i do think that on the Tansactional _bulk_docs status everything is clear now after Damien's clarifications. So please ASF members, chairs and CouchDB PMC members, if you have things to talk between you on how ASF projects are driven and if Cou

[jira] Updated: (COUCHDB-241) Add copy and move document in Futon

2009-02-06 Thread Patrick Antivackis (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Antivackis updated COUCHDB-241: --- Attachment: move.png copy.png COUCHDB-241.diff Here

[jira] Created: (COUCHDB-241) Add copy and move document in Futon

2009-02-06 Thread Patrick Antivackis (JIRA)
Reporter: Patrick Antivackis Priority: Minor Create features to copy and move a document directly from the Futon administrative interface using the COPY and MOVE couchDB features -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to

Re: streaming attachments writes

2009-01-18 Thread Patrick Antivackis
And what do you use to upload files bigger than 4 GB ? 2009/1/17 Benoit Chesneau > On Fri, Jan 16, 2009 at 10:54 PM, Patrick Antivackis > wrote: > > Damien, > > For what i saw in previous tests, if you not use the chunk method, then > you > > get an error caught

Re: streaming attachments writes

2009-01-16 Thread Patrick Antivackis
Damien, For what i saw in previous tests, if you not use the chunk method, then you get an error caught by mochiweb (so no error in couchdb). It occurs in mochiweb_request line 138 with the gen_tcp:recv call : recv(Length, Timeout) -> case gen_tcp:recv(Socket, Length, Timeout) of {ok,