consistently raise/warn for None in collection ?

This would be collection.append(None), s.add(Object(children=None)), etc. Maybe warn. cascade_iterator changes to support this, but also collections.py has lots of checks for None right now which would need to be adjusted.

See test/orm/test_cascades.py O2MCascadeTest for current behavior.

s = Session()
u1 = User(addresses=[None](None))
s.add(u1)
eq_(u1.addresses, [None](None))
s.commit()
# disappears, since persistence of None in 
# collection not supported
eq_(u1.addresses, [])

Comments (3)