Context Navigation

Changes between Initial Version and Version 1 of Ticket #36594

-              initial
+              v1
 That message implies that the value of False should work, so it is misleading.
 It turns out that boolean values of nulls_distinct are only acceptable for postgresql, which I missed when I first read the docs. It would be very helpful if the warning message included the information that boolean values of nulls_distinct are not acceptable for sqlite (or whatever database is triggering the warning).
+It turns out that boolean values of nulls_distinct are only acceptable for postgresql, which I missed when I first read the docs. It would be very helpful if the warning message included the information that boolean values of nulls_distinct are not acceptable for sqlite (or whatever database is triggering the warning) so the user knows how to fix the problem.
 Having the warning also include the information about the actual behavior is a nice touch (especially as the docs say that the behavior is for nulls to be distinct in most dbs), but the message should also include the root cause of the warning. That way the user knows how to fix the problem.
+Having the warning also include the information about the actual behavior is a nice touch, but is not the heart of the problem.
 Here is the simplest model I could come up with that shows the issue: