2017-12-06 15:46 GMT+01:00 Peter Da Silva :
> I’d recommend expr {double($temp)} so the bytecode compiler can optimize
> the expression.
>
> On 12/6/17, 8:40 AM, "sqlite-users on behalf of Cecil Westerhof" <
> sqlite-users-boun...@mailinglists.sqlite.org on behalf of
> cldwester...@gmail.com> wrot
I’d recommend expr {double($temp)} so the bytecode compiler can optimize the
expression.
On 12/6/17, 8:40 AM, "sqlite-users on behalf of Cecil Westerhof"
wrote:
return [expr double(${temp})]
___
sqlite-users mailing list
sqlite-users@mai
2017-12-06 14:58 GMT+01:00 Simon Slavin :
>
>
> On 6 Dec 2017, at 1:19pm, Cecil Westerhof wrote:
>
> >message NOT NULL
>
> Given thqt you want the "message" stored as REAL, you should be defining
> this column as REAL. This is necessary, though not sufficient.
I only want to
On 6 Dec 2017, at 1:19pm, Cecil Westerhof wrote:
>message NOT NULL
Given thqt you want the "message" stored as REAL, you should be defining this
column as REAL. This is necessary, though not sufficient.
Simon.
___
sqlite-users mai
2017-12-06 13:34 GMT+01:00 Darko Volaric :
> How it's stored depends on how the messages table is defined (which type
> the message column has been given), which you haven't shown, and whether
> storeMessage quotes the message argument when forming the string. My advice
> is to remove any column t
How it's stored depends on how the messages table is defined (which type
the message column has been given), which you haven't shown, and whether
storeMessage quotes the message argument when forming the string. My advice
is to remove any column type and make sure numbers are not quoted when they
a
6 matches
Mail list logo
