On 25 Nov 2013, at 11:58am, Luuk <luu...@gmail.com> wrote:
> On 24-11-2013 19:36, Petite Abeille wrote:
>>
>> On Nov 24, 2013, at 7:10 PM, Valentin Davydov <sqlite-u...@soi.spb.ru> wrote:
>>
>>> Wait a second... and you'll get different value of datetime('now'). In this
>>> sense datetime() is as deterministic as random(): it may give the same
>>> result
>>> next invocation or may not, dependng on various circumstances not related to
>>> the function itself.
>>
>> Nah… in SQL… ‘now’ is supposed to be computed once per statement. And that’s
>> all.
>
> Then 3.7.11, on windows is wrong, luckily this works OK on 3.8.1
Yes. This characteristic ('now' is evaluated once per statement) was discussed
and corrected recently. I too was surprise that SQL was specific about it
being evaluated just once for a statement. Though now I know that that, I'm
wondering whether there's an argument that it should be evaluated just once for
a transaction.
Simon.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
