eld) = datetime('2004-01-04
> >12:00:00')", does SQLite transform both to string and then do the
compare,
> >or does it transform both to floating point and then compare them?
> >
> >I ask that because I know there´s an overhead doing the type
DateTimeField FROM Allan
...> WHERE DateTimeField = julianday('2004-01-04 12:00:00');
2453009
sqlite>
-=-
Monday, January 5, 2004, 11:56:13 AM, you wrote:
> Got it!! =)
> Thank you so much again!!
> Roger.
> ----- Original Message -
> From: W All
Kurt Welgehausen wrote:
DRH wrote
The date and time functions ... are fully tested ...
I'm using SQLite version 2.8.8, precompiled binaries, on Linux.
The date/time functions seem to work, but some of the modifiers
don't. Specifically, 'gregorian', 'julian', 'start of week',
'localtime', and 'ut
DRH wrote
>> The date and time functions ... are fully tested ...
I'm using SQLite version 2.8.8, precompiled binaries, on Linux.
The date/time functions seem to work, but some of the modifiers
don't. Specifically, 'gregorian', 'julian', 'start of week',
'localtime', and 'utc' all cause the funct
Got it!! =)
Thank you so much again!!
Roger.
- Original Message -
From: W Allan Edwards
To: [EMAIL PROTECTED]
Sent: Monday, January 05, 2004 12:53 PM
Subject: Re: [sqlite] Date and Time functions are experimental
By my understanding of the code, it is turing into into
e typecast, so I would
like to choose what costs less, in my case.
Thanx!!
Roger.
- Original Message -
From: "D. Richard Hipp" <[EMAIL PROTECTED]>
To: "'SQLite Mailingliste'" <[EMAIL PROTECTED]>
Sent: Monday, January 05, 2004 11:37 AM
Subject: [
Allan Edwards wrote:
I looked through the source code and those functions "WERE" experimental.
They appear to be a full non experimental in the sqlite source code at this
point. Thus far I have not found any problems with them. You can #define
them out on a compilation if you don't want date rout
7 matches
Mail list logo
