mention that None!=None in UniqueConstraint tests

Issue #1181 resolved
Former user created an issue

The docs should mention that if you have a multiple columns listed in a UniqueConstraint and one of those columns contains a null/None/empty value then that constraint will never raise an IntegrityError.

Comments (2)

  1. Mike Bayer repo owner

    Looking more closely, this is really something to be documented by the relational database itself, and its not apparent to me that every RDBMS would even have this behavior. In any case its not a behavior defined by sqlalchemy.

  2. Log in to comment