That suggests that the script is not consistently telling sqlite which TZ to use in all calculations. i will take a look at it as time allows. Probably just need to be sure to consistently pass the final argument to strftime().
----- stephan (Sent from a mobile device, possibly from bed. Please excuse brevity, typos, and top-posting.) On May 8, 2016 21:34, "jungle Boogie" <jungleboogie0 at gmail.com> wrote: > On 8 May 2016 at 12:28, jungle Boogie <jungleboogie0 at gmail.com> wrote: > > I'll set the TZ on the pi to match and see what happens. > > We're on to something! > > pi time: > $ date > Sun May 8 12:29:54 PDT 2016 > > x86 time: > % date > Sun May 8 12:30:04 PDT 2016 > > > They match with cal.sql now! > http://kopy.io/GbbDR > > > So no problem with your script unless you're not using UTC time! > > -- > ------- > inum: 883510009027723 > sip: jungleboogie at sip2sip.info > xmpp: jungle-boogie at jit.si > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
