On Sat, Jan 3, 2015 at 5:23 AM, Simon Slavin <slav...@bigfraud.org> wrote:
> > On 3 Jan 2015, at 1:12am, J Decker <d3c...@gmail.com> wrote: > > > On Fri, Jan 2, 2015 at 4:44 PM, Simon Slavin <slav...@bigfraud.org> > wrote: > > > >> On 3 Jan 2015, at 12:12am, J Decker <d3c...@gmail.com> wrote: > >> > >>> https://www.sqlite.org/datatype3.html /* lists DateTime as a distinct > >>> type */ > > I'm going to answer this in detail because you still don't understand > what's happening and how to work with SQLite. > > I did. No new information there... > okay I wrote invalid times. I thought the colon was optional in the > > timezone offset portion > > All the values you supplied will be understood as strings. So given the > following values > > And they won't be parsed correctly by the date functions so using strftime() or datetime() resulted NULL... having the extra ':' allows the fucntions to work...and they all return self consistent strings that can be simply string compared > 2013-10-07 06:23:19.120 > 2013-10-07T01:23:19.120Z > 2013-10-07 08:23:19.120-04:00 > > they will be understood to be in this order: > > 2013-10-07 06:23:19.120 > 2013-10-07 08:23:19.120-04:00 > 2013-10-07T01:23:19.120Z > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
