Re: [sqlite] Odd behaviour with JulianDay

n says > a lot about anticipated traffic volume. > > >-Original Message- > >From: sqlite-users On > Behalf > >Of Stephen Chrzanowski > >Sent: Saturday, 7 September, 2019 14:12 > >To: sqlite-users > >Subject: Re: [sqlite] Odd behaviour with JulianDa

Re: [sqlite] Odd behaviour with JulianDay

calf >Sent: Saturday, 7 September, 2019 14:43 >To: SQLite mailing list >Subject: Re: [sqlite] Odd behaviour with JulianDay > > >You can convert a float unixepoch the same way as anything else, you just >need to tell strftime (or its overloaded aliases julianday and datet

Re: [sqlite] Odd behaviour with JulianDay

;s a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-Original Message- >From: sqlite-users On Behalf >Of Stephen Chrzanowski >Sent: Saturday, 7 September, 2019 14:12 >To: sqlite-users >Subject: Re: [sqlite] Odd behaviour with JulianDay

Re: [sqlite] Odd behaviour with JulianDay

I think I see it. This is the schema for the table: CREATE TABLE [EventEntry]( [EventID] INTEGER PRIMARY KEY AUTOINCREMENT, [IPAddress] CHAR, [Node] INTEGER DEFAULT 0, [NodeOpened] DATETIME, [NodeClosed] DATETIME); When I run a select * from EventEntry I'm seeing the 'float' since UnixE

[sqlite] Odd behaviour with JulianDay

I'm creating a new database to keep track of time difference between logins and logoffs for a particular system. I have the following query: select NodeOpened, JulianDay(NodeOpened), JulianDay('now') from EventEntry where NodeClosed is null The results are: NodeOpened