Hi,
this is the first announcement regarding the efforts to integrate L10N into
CouchDB. A new blog post is available [1] and we kindly ask you to like and
reshare the posts [2] in the different social media portals.
The efforts are still in a very early stage. The work on including the
creation
That should be sudo service couchdb start :-) From: Keith Gable
Sent: 11/9/2013 17:11
To: Alexander Gabriel; user@couchdb.apache.org
Subject: RE: CouchDb startup error: Failure to start Mochiweb
There should be an init script. Try:
service couchdb start
If that doesn't work:
sudo su -u couchdb cou
There should be an init script. Try:
service couchdb start
If that doesn't work:
sudo su -u couchdb couchdb From: Alexander Gabriel
Sent: 11/9/2013 15:27
To: user@couchdb.apache.org
Subject: CouchDb startup error: Failure to start Mochiweb
Hi experts
I've installed a droplet at digitaloceans.com
Hi experts
I've installed a droplet at digitaloceans.com using ubuntu 13.10, because
it is easy to install couchdb 1.4 on it as it's included in the software
repository.
So I ran "sudo apt-get install couchdb -y" and as far as I remember there
were no errors.
But when I run "sudo -i -u couchdb c
attachments are different to documents. They're stored as a series of
binary chunks and so they can be streamed in and out, you can go large
with attachments. The reason I say documents can't be too huge is that
couchdb has to hold them in memory to process them or even return
them.
As for comment
> sorting/displaying a comments thread with replies by appending the replies
within their respective original comment field.
Wouldn't it be more natural to use an array? And it would be more flexible
for possible future changes. It doesn't affect the size of the field but
there is no way a comme
Ok I was assuming the db could be really big. I'm storing images so it
_will_ get pretty large.
For the field size question: I had an idea to greatly simplify
sorting/displaying a comments thread with replies by appending the replies
within their respective original comment field. Since the order
while the default configuration has max_document_size as 4Gb, it would
be very unwise to make a document anywhere near that large. Database
size is limited only by disk capacity but note that you'll need some
free space for compacting the database.
On 9 November 2013 15:28, first-l...@yandex.ru w
Yes! It work for me on CouchDB 1.3.
But on CouchDB 1.4 not worked :(
Thanks!
Hm..it works for me on CouchDB 1.5, but as Robert said, using native
query server is dangerous and since it's completely undocumented and
may use internal CouchDB API there is no any warranties that code will
work corre
Base size in no limit. But file system may be limit by file size.
Doc size limit is 4Gb. (one or two or more field: total - 4Gb)
I have two storage questions. How big can any one field in one doc be?
Also, is there any limit on the size of a CouchDB? Meaning, if I have 1TB
of free disk space, wil
Hm..it works for me on CouchDB 1.5, but as Robert said, using native
query server is dangerous and since it's completely undocumented and
may use internal CouchDB API there is no any warranties that code will
work correctly in future releases.
--
,,,^..^,,,
On Sat, Nov 9, 2013 at 1:02 PM, first-l
I have two storage questions. How big can any one field in one doc be?
Also, is there any limit on the size of a CouchDB? Meaning, if I have 1TB
of free disk space, will the db grow to 1TB in size?
I want set limit base document count.
And now i see one way:
1) In Change Notifications function i see count document in base
2) if size of database larger given: replace validate_doc_update
function and denied create new docs.
It is long and slow way.
Maybe someone will tell a better implement
Deliberately not, no, a validate_doc_update function is only passed
the new document you're trying to update, the current one (if there is
one), the context of the user and the security object for the
database.
B.
On 9 November 2013 11:00, first-l...@yandex.ru wrote:
> And i not possible get in
And i not possible get information about data base from validate_doc_update?
validate_doc_update functions deliberately don't let you do this
otherwise eventually consistency can be compromised.
Also remember that the native view server has no sandbox, anyone
allowed to edit design documents can
validate_doc_update functions deliberately don't let you do this
otherwise eventually consistency can be compromised.
Also remember that the native view server has no sandbox, anyone
allowed to edit design documents can do anything to your servers that
the user you run couchdb as can (read files,
It is very good!
But, i create validation function and see error:
Error: EXIT
{{badmatch,[]},
[{couch_query_servers,new_process,3,
[{file,"couch_query_servers.erl"},{line,472}]},
{couch_query_servers,lang_proc,3,
[{file,"couch_query_servers.erl"},{line,462}]},
{couch_query_servers,handle_ca
17 matches
Mail list logo