I'm very interested in the idea of expanding the database level
constraints that can be supplied to a database schema, and also
automatically apply the same constraints to the model/view in django.
The various backends that support them, I believe already apply such
constraints for PositiveIntege
On Sep 26, 10:27 pm, Tim Chase wrote:
> > Is there anyone else interested in this?
>
> yes, I'd be interested in seeing some sort of database-level
> CHECK constraint as part of Django. I had been sitting on my
> thoughts until I see the GSoC work done on model-validation wend
> its way toward
On Nov 27, 10:07 pm, noel wrote:
> I really love this application Reinteract. Its an enhancement to
> Python Interactive Shell. And it would be lovely if I can use
> Reinteract with manage.py shell.
Have a look at bpython. I have a command set up where I can run
./manage.py bshell
And I get a
On Dec 15, 8:59 am, Sergiy Kuzmenko wrote:
> I wonder if there is a particular reason why last_login field of is not
> defined as "null=True"? It makes sense to me to have it as null which would
> mean that the user never logged in. Could there be any dependencies relying
> on this field not bein
On Dec 15, 8:59 am, Sergiy Kuzmenko wrote:
> I wonder if there is a particular reason why last_login field of is not
> defined as "null=True"? It makes sense to me to have it as null which would
> mean that the user never logged in. Could there be any dependencies relying
> on this field not bein
