Confirmed also. only happens on my 64-bit machine, and is not related
to apache at all as I can reproduce it faithfully in ipython.
On Dec 2, 8:32 pm, GRoby <[EMAIL PROTECTED]> wrote:
> I can confirm that all of my seg faults were all on my 64 bit machine
> but could not be duplicated when I trie
omly throw 500's, but not in any consistent way.
On Dec 3, 5:06 am, rcoup <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Dec 3, 5:21 pm, Andre P LeBlanc <[EMAIL PROTECTED]> wrote:
>
> > Confirmed also. only happens on my 64-bit machine, and is not related
> > to a
What about the patches on the ticket? The cookie-based approach is
not the right way to do it, as the comments on that page indicate,
these things should be stored server side, especially since it is
being unpickled serverside, it leave a larges security hole. (and the
encryption he later added
Sorry, I didn't notice that you said you didn't like the DB hits
associated with the session based approach, you can use memcached
sessions, or file-backed if avoid the database hits. :P
On Dec 5, 12:33 pm, Andre P LeBlanc <[EMAIL PROTECTED]> wrote:
> What about the patches
I think what you're trying to do can be accomplished with the
queryset's .extra() method.
something like
Level.objects.all().extra(select={'unlocked':'count(**matching rows in
the join table**) > 0'})
-Andre
On Dec 30, 7:04 am, Deniz Dogan wrote:
> Hi
>
> I have a user profile which has a many-t
5 matches
Mail list logo
