On 7/21/05, Chuck Pahlmeyer - MTI <[EMAIL PROTECTED]> wrote:
> I have an application in which I'd like to create a database as
> quickly as possible. The application has a batch process at
> startup which creates the data. I am using a single transaction
> for all of the INSERT statements. I'm
I have an application in which I'd like to create a database as
quickly as possible. The application has a batch process at
startup which creates the data. I am using a single transaction
for all of the INSERT statements. I'm also using prepared statements
to alleviate some of the overhead for
whalesong:~ brunij$ date
Thu Jul 21 13:40:42 MST 2005
whalesong:~ brunij$ sqlite3 /dev/null 'select current_time'
20:40:44
It works for me. I'm located at GMT-7. Where are you?
Perhaps what you wanted was:
select datetime('now','localtime');
On Jul 21, 2005, at 1:32 PM, Cyril Scetbon
Hi,
I don't understand why when I use select CURRENT_TIME from sqlite I get
a false value as follows :
[EMAIL PROTECTED]:~$ date
Thu Jul 21 22:37:20 CEST 2005
[EMAIL PROTECTED]:~$ sqlite3 /tmp/test.db "select CURRENT_TIME"
20:37:26
thanks
On Wed, 20 Jul 2005, Puneet Kishor wrote:
>
>I have never quite understood these LIMIT commands... how they would
>LIMIT without running the entire query anyway. If you want to
>constrain, the constrain should really be in the WHERE clause.
>
They are for reducing the result set size, very
5 matches
Mail list logo