I've been fiddling through Nabble, and I've been missing things. (Perhaps
it's me and not Nabble;(
You guys are WONDERFUL!
David, Igor, Alex; all have given me vital information and I very much
appreciate it!
Thanks!!
Dale
On Mon, Nov 2, 2009 at 4:24 PM, David Bicking <dbic...@yahoo.com> wrote:
> I probably should have explicitly stated that my suggestion only worked
> up to 24 hours. Unfortunately I couldn't think of a solution for greater
> values.
>
> Yesterday Igor posted a solution that works with days. You never
> responded to him so perhaps you didn't see it. I'll copy it here:
> ******
> SELECT
> cast(secs/86400 as integer) || '.' ||
> strftime('%H:%M:%f', secs ,'unixepoch') from
> (select SUM(tripSeconds) as secs from mytable);
>
> Igor Tandetnik
> ******
>
> You really can't go higher than "days" because months come in different
> sizes, as do years, i.e. months can be either 28, 29, 30 or 31 days
> depending on the time of year, etc.
> Years can be 365 or 366 days.
>
> If you want to make every MONTH=30 DAYS, well, you would need to do the
> math. Probably would be much easier to do in your application program
> than in SQL.
>
> Hopefully that helps.
>
> David
>
>
> On Mon, 2009-11-02 at 03:22 -0800, DaleEMoore wrote:
> > Hi David;
> >
> > That's LOVELY for small numbers like:
> >
> > SELECT STRFTIME('%H:%M:%f',62.5,'unixepoch')
> > 00:01:02.500
> >
> > What do you think I should do with larger periods of time? In the
> following
> > I hoped for 00-00-00.01:02.500.
> >
> > SELECT STRFTIME('%Y-%m-%d.%H:%M:%f',62.5,'unixepoch')
> > 1970-01-01.00:01:02.500
> >
> > I really appreciate hearing from you,
> > Dale
>
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
