Hi Niphlod,
Thank you for this information.
Could you tell me how you manage to copy new data into db from db2 after
finishing the scheduler job?
Thank you.
On Friday, November 9, 2012 at 10:31:03 AM UTC-5, Niphlod wrote:
>
> if you can, use a separate db for the scheduler. SQLite doesn't han
I guess if SQLite cannot handle many concurrent users while
writing/reading, should I move to postgres or mongoDB? There will be over
10k rows added every 10mins.
Thanks.
On Wednesday, October 14, 2015 at 10:03:30 PM UTC-4, kenny c wrote:
>
> Hi Niphlod,
>
> Thank you for this information.
>
>
mongodb isn't a supported backend for the scheduler.
And to answer your previous request: db2 is there just to support scheduler
"internals" . if your task still wants to write to db there's nothing wrong
with it.
On Thursday, October 15, 2015 at 4:39:17 AM UTC+2, kenny c wrote:
>
> If SQLite ca
if you can, use a separate db for the scheduler. SQLite doesn't handle well
concurrent writes (with default operational capabilities), so having the
scheduler operating on the same database of your "insertion" of messages
can lead to locks.
Just do
db = DAL('whatever.db')
db2 = DAL('whatever_
Thank you again Niphlod. That seems like a sensible way for me to separate
the two out. I'll give that a try.
On Friday, 9 November 2012 10:31:04 UTC-5, Niphlod wrote:
>
> if you can, use a separate db for the scheduler. SQLite doesn't handle
> well concurrent writes (with default operational ca
5 matches
Mail list logo
