Re: [SQLObject] Default Behaviour when notNull == False

[Luke O. <lu...@me...>]

> To me:
>
>     default=None
>
> reads essentially "if no value is specified, this column has no
> value", which is redundant. I think it would be reasonable for
> SQLObject to internalize the default=None

To me, "None is NULL" for SQLObject, so it reads "if no value is
specified, this column is NULL".  notNull=False is still independent
of this: I take default to mean "you don't need to be explicit in
setting this field, we have a default". You could easily have a field
that CAN have a NULL (notNull=False), but that you still want people
to explicitly declare. In my mind.

- Luke