Hi Florian,
Thanks for your remind, hope this ticket can be reviewed soon.
Regards,
Robert
On Tue, Nov 20, 2012 at 8:00 PM, Florian Apolloner
wrote:
> Hi Robert,
>
> there is no need to notify us about tickets here, we do see those in Trac ;)
>
> Best Regards,
> Florian
>
> --
> You received th
Hi Robert,
there is no need to notify us about tickets here, we do see those in Trac ;)
Best Regards,
Florian
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django
Hi,
We found there are lots of empty records(load() returns an
empty dict) in django_session table.
We suspect it was caused by invalid session keys sending by our users.
I created ticket #19324(which I copied below) to describe the problem:
https://code.djangoproject.com/ticket/19324#ticket
On Tue, Apr 29, 2008 at 1:48 PM, Ed Menendez <[EMAIL PROTECTED]> wrote:
...
> django_session.session_data is made a char(40) instead of a
> varchar(40) most DB engines will make that row a fixed length row
Ed, session_data uses various (non varchar) field types.
I think you must mean session_k
We might want to consider a performance boost for those that choose to
use the django_session table over memcached. If
django_session.session_data is made a char(40) instead of a
varchar(40) most DB engines will make that row a fixed length row
(longtext/blobs are stored outside the row with a
