Ian Strascina wrote:
> So is this a sqlite bug in that inconsistent results are coming from queries
> that should be functionally equivalent according to the above documentation
Realize that SQLite doesn't have a date or datetime data types. All the
calculations are
>It's a pain in the arse that one has to pay for copies of the
>ISOs. What do they think we're paying them for ?
I also find this a perverse effect totally contrary to their mission or
at least its spirit: produce good standards for public use. Without
free access to reference up-to-date
On 2 Apr 2011, at 4:30pm, Simon Slavin wrote:
> The ISO standard separates date and time with exactly 'T' or 't'.
Wrong. Sorry about that. The ISO standard specifies a capital 'T'. Other
standards which are obviously based on it suggest that a lower-case 't' is
acceptable. Apologies for
On 1 Apr 2011, at 11:31pm, Ian Strascina wrote:
> I have come across inconsistent results of queries using datetime functions
> and
> values. I have based everything I tested off of this page:
> http://www.sqlite.org/lang_datefunc.html
There's a problem with that web page. The ISO standard
I have come across inconsistent results of queries using datetime functions and
values. I have based everything I tested off of this page:
http://www.sqlite.org/lang_datefunc.html
I have a table with a /start_date/ property. The values written are UTC time
of
the format
5 matches
Mail list logo