Re: Update Status Field after Expiry Date
- From: Ed Murphy <emurphy42@xxxxxxxxxxxx>
- Date: Thu, 29 Mar 2007 18:08:00 -0700
--CELKO-- wrote:
All data types have to be NULL-able in SQL. Having a BOOLEAN type
would lead to 4 valued logic with inconsistent rules about how NULLs
propagate. And the various vendor extension do not work or port
either.
It seems like dropping UNKNOWN would leave a sensible set of rules:
and | T N F or | T N F not |
----+------ ---+------ ----+--
T | T N F T | T T T T | F
N | N N F N | T N N N | N
F | F F F F | T N F F | T
Am I overlooking anything?
.
- References:
- Update Status Field after Expiry Date
- From: shane . taylor81
- Re: Update Status Field after Expiry Date
- From: Erland Sommarskog
- Re: Update Status Field after Expiry Date
- From: shane . taylor81
- Re: Update Status Field after Expiry Date
- From: --CELKO--
- Update Status Field after Expiry Date
- Prev by Date: Re: Run query based on values in another table
- Next by Date: Re: pivot table without aggregation?
- Previous by thread: Re: Update Status Field after Expiry Date
- Next by thread: SQL Server Problem
- Index(es):
Relevant Pages
|
