2012/4/12, Alexey Pechnikov :
> May be used "onecolumn" function instead of "eval". The "eval" function
> returns empty value of single record and so the result is "{}".
"Empty list", I suppose?
--
regards,
Zbigniew
___
2012/4/12, Richard Hipp :
> On Thu, Apr 12, 2012 at 2:06 PM, Zbigniew wrote:
>
>> At the attempt to get a non-existing value, for example:
>>
>> set x [dbcomm eval {SELECT max(somecolumn) FROM sometable}]
>>
>
> The correct way to do this would be one or
On Thu, Apr 12, 2012 at 2:15 PM, Richard Hipp wrote:
>
>
> On Thu, Apr 12, 2012 at 2:06 PM, Zbigniew wrote:
>
>> At the attempt to get a non-existing value, for example:
>>
>> set x [dbcomm eval {SELECT max(somecolumn) FROM sometable}]
>>
>
> The correct
On Thu, Apr 12, 2012 at 2:06 PM, Zbigniew wrote:
> At the attempt to get a non-existing value, for example:
>
> set x [dbcomm eval {SELECT max(somecolumn) FROM sometable}]
>
The correct way to do this would be one or other other of the following:
set x [lindex
May be used "onecolumn" function instead of "eval". The "eval" function
returns empty value of single record and so the result is "{}".
2012/4/12 Zbigniew
> At the attempt to get a non-existing value, for example:
>
> set x [dbcomm eval {SELECT max(somecolumn) FROM
At the attempt to get a non-existing value, for example:
set x [dbcomm eval {SELECT max(somecolumn) FROM sometable}]
The returned value of $x will be {} - and no, not "empty", but exactly
these two characters.
Easy to reproduce.
--
Zbigniew
___
6 matches
Mail list logo