On Mar 14, 8:04 am, Sergio wrote:
> wow, that's interesting. I was not aware if this.
>
> So, coming to the real question, here is my use case which raised this
> questions:
>
> I've a class in the model with two CharFields. When validating data
> inputs, I need to check that, if the user filled
wow, that's interesting. I was not aware if this.
So, coming to the real question, here is my use case which raised this
questions:
I've a class in the model with two CharFields. When validating data
inputs, I need to check that, if the user filled field A, then also
field B should contains some
On Fri, 2009-03-13 at 19:29 -0700, Sergio wrote:
>
>
> On Mar 14, 2:23 am, Malcolm Tredinnick
> wrote:
> > Character fields in Django can never be NULL. They will either be empty
> > (and stored as '') or not empty, but never stored as NULL in the
> > database.
>
> thanks for your answer. Coul
On Mar 14, 2:23 am, Malcolm Tredinnick
wrote:
> Character fields in Django can never be NULL. They will either be empty
> (and stored as '') or not empty, but never stored as NULL in the
> database.
thanks for your answer. Could you please give more insight on this
note?
"When using the Oracl
On Fri, 2009-03-13 at 16:51 -0700, Sergio wrote:
> Hello,
>
> reading from this page:
> http://docs.djangoproject.com/en/dev/ref/models/fields/#null
>
> I understand that, at validation time, I could use (variable is not
> None) to verify whether the user did enter characters or not.
>
> Consid
Hello,
reading from this page:
http://docs.djangoproject.com/en/dev/ref/models/fields/#null
I understand that, at validation time, I could use (variable is not
None) to verify whether the user did enter characters or not.
Considering the note, it seems that, in case of oracle DB, I should
use (
6 matches
Mail list logo
