On Saturday, June 4, 2016 at 12:12:42 AM UTC+2, Cristiano Coelho wrote:
>
> Aymeric, I have never said anything about connection pool, I'm talking
> about thread pooling to perform async work
>
I have similar requirements and issues with Django. It looks like it is
completely unreliable in async environment, and the worst thing is that I
can't force Django to create new connection within the thread/process. I'm
fighting with this almost day by day, enssuring that no db operation is
performed in asyncs callbacks, and I'm using ram to return results to main
thread/process and then write them to db.
Well, they'll say that Django is not designed for that cases. Maybe. My
advise - don't use Django for medium and big projects. Using Django for
that job was my biggest mistake. From version to version it turns more
into handy tool for blog creators/webdesigners, forcing everyone else to
(for example) do nasty things with your database ("I'm a Django and I own
your database, ha ha!").
Marcin
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/3e6c1b86-fbb8-466f-9fee-c54363bf8ef1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
