Ken wrote:
sum(is_complete) is only the same as "where is_complete = 1" when there is
a check constraint guaranteeing that is complete will either be a 0 or 1.
Yes, that is true, and you could sum(is_complete != 0) if you want to be
extra careful. This uses a C like definition of true as anything except
zero.
I think its reasonable for an application to assume that a database
field has a suitable value if it's the application that puts those
values (i.e. 0 or 1 only for a boolean column) into the database.
Dennis Cote
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
