[seam-dev] Seam 2.1.1.CR2

Francisco Jose Peredo franciscoperedo at tabasco.gob.mx
Thu Dec 4 14:13:46 EST 2008


An outer join where the column in the join is a *nullable boolean*? Can
you give me an example where doing that is better (easier to understand
during maintenace) than using an integer? I do not go against all nulls,
just *boolean *nulls.

Gavin King escribió:
> So you never use outer joins? Every outer join produces null values.
>
> On Thu, Dec 4, 2008 at 1:04 PM, Francisco Jose Peredo
> <franciscoperedo at tabasco.gob.mx> wrote:
>   
>> I try to avoid it in databases, if there are 3 different possible
>> values, it is better to use a not null Integer column, all my boolean
>> columns are "not null" always.
>>
>> Emmanuel Bernard escribió:
>>     
>>> Databases use this three-state for decades. It seems to work fine.
>>>       
>> Many people believe it does not work fine:
>> http://en.wikipedia.org/wiki/Null_(SQL)#Controversy
>>     

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20081204/c06c0f5c/attachment.html 


More information about the seam-dev mailing list