On 14 Jul 2010, at 7:22pm, Richard Hipp wrote:
> On Wed, Jul 14, 2010 at 1:25 PM, Simon Slavin wrote:
>
>> By the way, can someone explain why this rule, equivalent to line 4 of the
>> table, is there:
>>
>> elseif the right op contains NULL, then IN = NULL
>
>
On Wed, Jul 14, 2010 at 1:25 PM, Simon Slavin wrote:
> By the way, can someone explain why this rule, equivalent to line 4 of the
> table, is there:
>
> elseif the right op contains NULL, then IN = NULL
>
> By the time we've got there we already know that the left
On Jul 15, 2010, at 12:25 AM, Simon Slavin wrote:
>
> On 14 Jul 2010, at 5:13pm, Richard Hipp wrote:
>
>> Improvements to the IN operator documentation can be found here:
>>
>>http://www.sqlite.org/draft/lang_expr.html#in_op
>
> I find that table difficult to understand: you have some
On 14 Jul 2010, at 5:13pm, Richard Hipp wrote:
> Improvements to the IN operator documentation can be found here:
>
> http://www.sqlite.org/draft/lang_expr.html#in_op
I find that table difficult to understand: you have some mutually exclusive
columns. Could it be replaced by this
On Wed, Jul 14, 2010 at 8:17 AM, Igor Sereda wrote:
>
> On page http://www.sqlite.org/lang_expr.html :
>
> "When a SELECT is the right operand of the IN operator, the IN operator
> returns TRUE if the SELECT result contains no NULLs and if the left operand
> matches any of the
On page http://www.sqlite.org/lang_expr.html :
"When a SELECT is the right operand of the IN operator, the IN operator
returns TRUE if the SELECT result contains no NULLs and if the left operand
matches any of the values in the SELECT result."
The part "SELECT result contains no NULLs" does not
6 matches
Mail list logo