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

[Nick <ni...@dd...>]

On Wed, 2003-04-30 at 08:55, Brad Bollenbach wrote:
> Can we change the behaviour of this to "feel" more like an SQL insert,
> so that if a column's allowed to be null, I don't have to specify it
> in the new()?

This patch should do what you want.  Note that I've changed notNull to
default to True instead of False, because it seems to make more sense to
do so.  If you *don't' specify a keyword argument to new, I would think
you would *want* to see an error there instead if you didn't
specifically tell it to not expect one.

Nick