I often found this handy too. Here's my implementation on bitbucket[1].
There are tests[2] and documentation[3]. It's something I wanted propose to
Django core as well but never found time to do so. :)
In my implementation I chose to assign numeric values explicitly:
Agreed - if we were going to implement this, we'd use a bit string
implementation, not push it into a char field.
Yours,
Russ Magee %-)
On Sat, Nov 2, 2013 at 4:22 AM, Michael Manfre wrote:
> Storing bits as a string is not an efficient use of space and is slower to
>
Storing bits as a string is not an efficient use of space and is slower to
query. Any reason why you are not using the bit datatype with a length?
E.g. 'bit(%s)' % len(self.flags)
Regards,
Michael Manfre
On Fri, Nov 1, 2013 at 3:50 PM, Paul Kenjora wrote:
> Hi,
>
> I'd
Hi,
I'd like to propose a new field type I've used on several projects. Its
a list of boolean flags all in one field. It replaces the need for many
Boolean fields and has the same basic DB lookup capabilities. This is
fully Admin compatible and Database agnostic.
Here is the full code,
On 1 November 2013 14:22, Florian Apolloner wrote:
First of all, using prefork and daemon mode is probably not the best choice
> you can make. I'd assume you are storing state in the process in your auth
> backend somehwere…
>
Prefork thanks to php, which is used to
First of all, using prefork and daemon mode is probably not the best choice
you can make. I'd assume you are storing state in the process in your auth
backend somehwere…
On Friday, November 1, 2013 11:30:04 AM UTC+1, HM wrote:
>
> I have an auth-backend inheriting from model backend that works
I have an auth-backend inheriting from model backend that works on 1.3.x
and 1.4.x but does not work on 1.5.x. The only difference between the
systems is the version of Django.
After much comparing and cursing and tearing of hair, it turns out what has
changed is how Django behaves under mod_wsgi