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

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

> Yes, but "NULL" is just computerese for "no value". :)

Maybe in your world. :) Ok, I guess I'll concede for now. Was this
whole discussion just about whether notNull=False should imply
default=None? I'm still not convinced that my statement: "a field
that CAN have a NULL (notNull=False), but that you still want
explicitly declared (no default)"  is useless or gibberish, but
that's probably such a rare case that .... screw 'em.

It only comes up because "default" is overloaded to both provide a
default value and to control explict definition in the object
interface, but I can't think of a non-rediculous way to separate
these.

- Luke