Hi everybody,
my server running some days then crashes and I have to restart.
I enclosed the crash report. I cannot read out whats causing the problem.
Maybe someone could give me a hint?
Thanks in advance
Marcus
) discusses how he designed it (I think it
was a talk at MIT?). It’s really interesting from a design and development
perspective.
Marcus
> On 12. Mar 2020, at 18:27, Joan Touzet wrote:
>
> Hi Garren, thanks for thinking ahead on this one.
>
>> On 2020-03-12 10:32, Garren Smit
Hi Jan,
thanks for your quick reply!
Updating the _security object did the trick. Thanks alot!
Am 10.03.2020 um 12:09 schrieb Jan Lehnardt:
Heya Marcus,
Newly created databases are admin-only by default in 3.0 (which is
different from 2.x):
https://blog.couchdb.org/2020/02/26/the-road-to
.
Now I get on the same call:
{
"error": "unauthorized",
"reason": "You are not authorized to access this db."
}
Did I miss / forget something.
Is this a problem caused by changes in 3.0 or could this be a problem of
the ssl?
Can someone help me please.
Thanks in advance and kind regards
Marcus
t, it is tempting
to let each user store their data in a separate database under the application
account. That works well, mostly, if the number of users is small."
Source: https://www.ibm.com/cloud/blog/cloudant-best-and-worst-practices-part-1
What are your personal experiences with large numbers of databases?
Marcus
one could share their working solutions it would
be a great help.
Marcus
> On 9. Feb 2020, at 09:04, Willem van der Westhuizen wrote:
>
> I would like to follow up on the Cloudant suggestion of a per-user database.
> That seems in contrast to other couchdb resources advocating
Travis, that sounds like a solution that might work for my project. Are you
able to share any of the code for your middleware?
Marcus
> On 9. Feb 2020, at 01:25, Travis Klein wrote:
>
> One option would be to have a node express server as middleware.
to lists.
Cloudant strongly advise against creating one database per user, unless it's a
very small number. They suggest a limit of 500 databases to not diminish
performance.
Does anyone have a suggestion how I could control read access for each to-do
list?
Thanks,
Marcus
> On 06 Dec 2014, at 16:08, Alexander Shorin wrote:
>
> This isn't valid JSON object, but Python dict representation. Try to
> json.dumps it before send. Also content_type should be string, not
> None.
Oh, the missing content-type was actually a problem oO. Thanks a lot!
> On 06 Dec 2014, at 1
[{file,"couch_db.erl"},{line,776}]}]
[Sat, 06 Dec 2014 13:44:24 GMT] [info] [<0.2781.0>] 127.0.0.1 - - POST
/my-nice-table/_bulk_docs 500
[Sat, 06 Dec 2014 13:44:24 GMT] [error] [<0.2781.0>] httpd 500 error response:
{"error":"unknown_error","reason":"badarg”}
Other JSOM-objects without an attachment can be successfully submitted to the
tabel.
Does anyone have an idea what’s going wrong?
Best Regards
Marcus
uot;dbname").allDocs({ ... });
Marcus
On Wed, Nov 3, 2010 at 6:17 PM, Paul Davis wrote:
>
> Can you check the logs to see what the URL was that was requested?
Do you mean web server logs? I'm using couchone hosting and don't have
access to server logs. Does CouchDB keep request logs accessible via
Futon?
Thanks,
Marcus
un 2009, at 23:03, Marcus Persson Lindqvist wrote:
>
> Greetings all!
>>
>> In short - what factors are involved in memory consumtion for couchdb for
>> a
>> large (x * 1000+) number of databases? Any hints welcome.
>>
>
> Each database requires a file ha
ple view. (Are there any
"trivial" build-in way of getting documents i reversed insertion-order btw?)
And yeah, the load for most databases is really low, so insert/output
performance could be compromized for less memory consumtions.
Any hints, tips or experiences?
Marcus
14 matches
Mail list logo
