Changes between Initial Version and Version 1 of Ticket #36592, comment 4


Ignore:
Timestamp:
Sep 3, 2025, 11:22:46 PM (37 hours ago)
Author:
Russell Owen

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36592, comment 4

    initial v1  
    33The bug is that one cannot construct a `UniqueConstraint` in sqlite if one specifies a boolean value for the `nulls_distinct` argument, even if the boolean value matches the behavior that sqlite supports. The only accepted value is None, and that is needlessly limiting.
    44
    5 Based on the warning message that is printed, I believe that an explicit value of False should also be accepted. If I misunderstand and got the sign wrong, the bug still should be fixed. The *compatible* boolean value of `nulls_distinct` should be acceptable. It should result in the constraint being generated, without any warning.
     5Based on the warning message that is printed, I believe that an explicit value of `False` should be accepted. If I misunderstand and got the sign wrong, the bug still should be fixed. The *compatible* boolean value of `nulls_distinct` should be acceptable. It should result in the constraint being generated, without any warning.
    66
    77Use cases for specifying an explicit boolean value for `nulls_distinct` include:
Back to Top