On Tuesday 05 July 2005 01:23 pm, jack wu wrote:
> one more question if i may. what should i do if i 'd
> like to have two columns, one for Date, one for Time
> of the day. most of the times, i 'd like to query by
> Date only but i want to display date and time at the
> same time. is julianday('2005-07-01') going to store
> any time information? Thanks.
yes it does.
sqlite> select datetime(julianday('2005-07-01'));
2005-07-01 00:00:00
time is midnight ;)
>
> jack.
>
> --- Stephen Leaf <[EMAIL PROTECTED]> wrote:
> > On Tuesday 05 July 2005 09:53 am, Cory Nelson wrote:
> > > Just an educated guess, but probably because
> >
> > sqlite tries to be as
> >
> > > minimal as possible. Which I have no complaints
> >
> > with, as comparing a
> >
> > > double will likely be faster than comparing a
> >
> > string.
> > I personally store all mine like this anyway using
> > unix time so I can change
> > the format at anytime. plus it's not only faster to
> > compare programming wise,
> > just compare numbers. no need use functions.
> > strings also are larger than numbers in size wise so
> > you save a few bytes here
> > and there.
> >
> > > On 7/5/05, Johan Danielsson <[EMAIL PROTECTED]>
> >
> > wrote:
> > > > Cory Nelson <[EMAIL PROTECTED]> writes:
> > > > > create table t_foo(bar real);
> > > > > insert into t_foo
> >
> > values(julianday('2005-07-01'));
> >
> > > > Is there any advantage to this compared to
> >
> > storing dates as strings in
> >
> > > > (for instance) ISO8601 format?
> > > >
> > > > /Johan
