Hi Mathias
I think that this ( allow_jsonp ) is what you require to add to your
local.ini or within local.d.
Please re-check CouchDB documentation.
[httpd]
;port = 5984
;bind_address = 127.0.0.1
bind_address = 0.0.0.0
allow_jsonp = true
Regards,
PECastro
On 04/05/11 23:16, Matt
Hi everybody,
I'm a litte desperate. Perhaps you could help me. I'm now trying for
hours to connect to a couchdb server via javascript.
Do you have a good example how I can perform a JSON call to a database
in JS? I tried several libraries like accompagnied couch.js, jqcouchdb
(http://plugins.jque
On 05/04/2011 04:13 PM, Eli Stevens (Gmail) wrote:
> 11:59 - Document D inserted on Node 2. Replication hasn't happened yet.
> 12:00 - First access of view page 1 on Node 1. Only A, B, C are present.
> 12:01 - D is replicated to Node 1.
Mmm, yes, you're absolutely correct; depending on that view
On Wed, May 4, 2011 at 10:41 AM, Owen Marshall
wrote:
> So, if a user runs this view on N1 at 12:00, and changes/adds are
> replicated in from N2 at 12:01, **it doesn't matter!** Those documents
> will have an updatetime > 12:00, so they won't be seen.
This isn't the use case being described thou
Not sure that's quite exactly what we need to do.
Mike's concept is relatively spot on..
the since= is a constantly changing result if I understand it
correctly, as updates/insertions occur, the sequence is incremented.
If I use an example timeline:
0-10-20-30-40->
How wo
This feature exists.
Query the view with ?update_seq=true, and you will get a line in the
output that tells you what the DB seq the view is current as of.
Then you can subscribe to filtered changes with since= the seq, and
have a continuously updated transactional view of the view.
Cheers,
Chris
On 05/04/2011 12:36 PM, Jim Klo wrote:
> We need to be able to paginate through that range and be guaranteed that it's
> not going to be modified via some update happening in another thread.
>
>[...] I request a range of objects at 12:00pm... I need to be able to paginate
>through that range pro
What you are describing could be resolved with a feature (that I believe
does not exist).
If you could supply a database sequence number when querying a view
ie. return the results from the view when the database sequence number
was "x" then the MVCC guarantees of couchdb would guarantee exactly
I might be able to shed some light here, as I'm working w/ John on this project.
Essentially I believe ultimately we need to be able to do is build a view that
is similar to the _changes but filtered.
Basically we need a way to maintain 'local' transactional integrity. So
assuming our Couch is
Owen,
Thank you for all replies. I answered inline
-Original Message-
From: Owen Marshall [mailto:omarsh...@facilityone.com]
Sent: Wednesday, May 04, 2011 12:15 PM
To: user@couchdb.apache.org
Cc: Poyau, John
Subject: EXTERNAL: Re: Document Timestamp On Replication
On 05/04/2011 11:29 A
On 05/04/2011 11:29 AM, Poyau, John wrote:
> -We want to keep track of the time that a document is added/updated in a
> source database
Then you definitely want an updated field per-document.
Implementing this varies with your needs. You could use a single
timestamp that gets clobbered each time
There's definetly a config file missing. You can check your config
settings (and paths) when you run your couch in debug log level.
Cheers,
Volker
On 05/04/2011 05:05 PM, e0075...@student.tuwien.ac.at wrote:
> Tanks for your help Volker. It seems to solve the problem. Is it normal
> that I get
-Original Message-
From: Owen Marshall [mailto:omarsh...@facilityone.com]
Sent: Wednesday, May 04, 2011 10:33 AM
To: Poyau, John
Cc: user@couchdb.apache.org
Subject: EXTERNAL: Re: Document Timestamp On Replication
On 05/03/2011 04:54 PM, Poyau, John wrote:
> Thank you for your reply. I
Tanks for your help Volker. It seems to solve the problem. Is it
normal that I get warnings because of unused variables? Because
spatial queries don't seem to work and I get this error:
{"error":"not_found","reason":"missing handler: _spatial"}
I've copied all files and set the ERL_FLAGS as s
You seems to miss packages, this might help:
http://www.ejabberd.im/undef-make-all
Cheers,
Volker
On 05/04/2011 04:30 PM, e0075...@student.tuwien.ac.at wrote:
> Ah yeah sry that I didn't specified that.
>
> I've already complied and installed CouchDB 1.0.2 without any problems.
> I've also tes
On 05/03/2011 04:54 PM, Poyau, John wrote:
> Thank you for your reply. I am aware of the issue that you mentioned and
> that is why I posted my question to list.
>
> One approach that I thought of is to use a separate document to hold the
> update_timestamp,
> these documents would not get rep
Ah yeah sry that I didn't specified that.
I've already complied and installed CouchDB 1.0.2 without any
problems. I've also tested it and it works without any problems.
I'm currently stuck at compiling GeoCouch. I've followed the
installation instruction specified within the readme file.
On 05/04/2011 04:17 PM, e0075...@student.tuwien.ac.at wrote:
>
> Hello,
> my name is Bernhard, I'm currently writing my bachelor thesis in
> Geoinformatics where I use GeoCouch within my project. After the new
> Ubuntu release I also decided to upgrade my GeoCouch server. But when
> trying to comp
Hello,
my name is Bernhard, I'm currently writing my bachelor thesis in
Geoinformatics where I use GeoCouch within my project. After the new
Ubuntu release I also decided to upgrade my GeoCouch server. But when
trying to compile the source code with make I get the following error
message:
Jeroen Janssen writes:
>
> Hi Peter,
>
> Did you happen to have time for updating the epel-couchdb repository
> to 1.0.2 yet?
>
> Best regards,
>
> Jeroen Janssen
>
> On Tue, Feb 8, 2011 at 2:57 PM, Peter Lemenkov wrote:
> >
> > I'll update it in a couple of days (more likely during this we
20 matches
Mail list logo
