Eugene Lazutkin wrote:
>Woot! 1539 and 1442 are both committed! Now all multithreaded guys, and
>MySQL users can start up projects right out of the box without digging
>for "magic incantations" in tickets, mail lists, and blogs!
>
>
Woots and thanks to Adrian and Eugene from me too :-)
I hop
Adrian Holovaty wrote:
>
> Thanks, guys! I've commited that.
Woot! 1539 and 1442 are both committed! Now all multithreaded guys, and
MySQL users can start up projects right out of the box without digging
for "magic incantations" in tickets, mail lists, and blogs!
Thanks,
Eugene
--~--~-
On 3/25/06, Eugene Lazutkin <[EMAIL PROTECTED]> wrote:
> The patch is in the Trac: http://code.djangoproject.com/ticket/1539.
> I've submitted both versions for the Django trunk and the magic-removal
> branch.
>
> Big thanks to Alex Brown for finding the bug and testing the fix.
Thanks, guys! I'v
The patch is in the Trac: http://code.djangoproject.com/ticket/1539.
I've submitted both versions for the Django trunk and the magic-removal
branch.
Big thanks to Alex Brown for finding the bug and testing the fix.
Thanks,
Eugene
Alex Brown wrote:
> Ivan Sagalaev wrote:
>> I think so too...
Ivan Sagalaev wrote:
> I think so too... I was investigating Alex's report and it looks like
> somewhere onr thread is creating a QueryDict and another tries to access
> it while it's being created. It's the only place where it doesn't
> contain self._mutable.
>
> This may mean that mod_python som
Ivan Sagalaev wrote:
>>
> I think so too... I was investigating Alex's report and it looks like
> somewhere onr thread is creating a QueryDict and another tries to access
> it while it's being created. It's the only place where it doesn't
> contain self._mutable.
>
> This may mean that mod_pyt
Eugene Lazutkin wrote:
>Alex: I'll look into this problem. Most probably there is a racing
>condition in multithreaded Django. It doesn't look like it is related to
>database backends.
>
I think so too... I was investigating Alex's report and it looks like
somewhere onr thread is creating a Qu
Alex Brown wrote:
>
> Let me know if there is anything I can do to help.
In e-mail.
Thanks,
Eugene
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to djang
Eugene Lazutkin wrote:
> Alex Brown wrote:
> > Eugene Lazutkin wrote:
> >
> >> Alex Brown wrote:
> >>> I am running django on a Windows server (apache 2.0.54/mod_python
> >>> 3.1.3/postgres 8.0.3)
> >>>
> >>> Django would crash apache when running multiple automated scripts
> >>> POSTing data at a
Alex Brown wrote:
> Eugene Lazutkin wrote:
>
>> Alex Brown wrote:
>>> I am running django on a Windows server (apache 2.0.54/mod_python
>>> 3.1.3/postgres 8.0.3)
>>>
>>> Django would crash apache when running multiple automated scripts
>>> POSTing data at a high rate through a generic create_obje
Eugene Lazutkin wrote:
> Alex Brown wrote:
> > I am running django on a Windows server (apache 2.0.54/mod_python
> > 3.1.3/postgres 8.0.3)
> >
> > Django would crash apache when running multiple automated scripts
> > POSTing data at a high rate through a generic create_object view.
> >
> > After
Alex Brown wrote:
> I am running django on a Windows server (apache 2.0.54/mod_python
> 3.1.3/postgres 8.0.3)
>
> Django would crash apache when running multiple automated scripts
> POSTing data at a high rate through a generic create_object view.
>
> After scanning the net I found various threa
I am running django on a Windows server (apache 2.0.54/mod_python
3.1.3/postgres 8.0.3)
Django would crash apache when running multiple automated scripts
POSTing data at a high rate through a generic create_object view.
After scanning the net I found various threading fix patches, and I
ended up
13 matches
Mail list logo
