Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-30 Thread sankara . narayanan

Return Receipt
   
Your  Re: [sqlite] Versions 2.8.15 and 3.0.3 available 
document   
:  
   
was   Sankara Narayanan/BTC/PIN/PHILIPS
received   
by:
   
at:   30/07/2004 12:51:05 ZE5B 
   






Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-26 Thread Doug Currie
Monday, July 26, 2004, 5:46:48 PM, Nuno Lucas wrote:
> Doug Currie, dando pulos de alegria, escreveu :
>> In 3.x column names are available as soon as the query is prepared.
>> See the C API reference at
>> http://www.sqlite.org/capi3ref.html#sqlite3_column_name

> This wasn't implemented in 3.0.2, right? (I didn't test 3.0.3 yet)

> I believe I tried that (exactly because I understood that from the docs)
> but found it didn't work for empty tables.

Please try it again; I just tried it with an sqlite3 I built on June
24, and it is working...

Lua 5.0.2  Copyright (C) 1994-2004 Tecgraf, PUC-Rio
> require"sqlite3"
> db=sqlite.open"foo.db"
> db:exec"create table baz (a,b,c);"
> vm=db:compile"select * from baz;"
> t=vm:get_names()
> for i,n in pairs( t) do print (i,n) end
1   a
2   b
3   c
n   3

e




Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-26 Thread Nuno Lucas
Doug Currie, dando pulos de alegria, escreveu :
In 3.x column names are available as soon as the query is prepared.
See the C API reference at
http://www.sqlite.org/capi3ref.html#sqlite3_column_name
This wasn't implemented in 3.0.2, right? (I didn't test 3.0.3 yet)
I believe I tried that (exactly because I understood that from the docs) 
but found it didn't work for empty tables.

Regards,
~Nuno Lucas


Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-26 Thread Roger Reghin \(Duty/Sedes/CWB\)
Great!!! Thanks!

Roger.


- Original Message - 
From: "Doug Currie" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 26, 2004 4:10 PM
Subject: Re: [sqlite] Versions 2.8.15 and 3.0.3 available


>
> Monday, July 26, 2004, 12:33:41 PM, Roger Reghin wrote:
>
> > I also use EMPTY_RESULT_CALLBACKS for the same reason Nuno does. And my
> > software also needs FULL_COLUMN_NAMES as well. So, no 3.x for me... =(
>
> In 3.x column names are available as soon as the query is prepared.
> See the C API reference at
> http://www.sqlite.org/capi3ref.html#sqlite3_column_name
>
> > const char *sqlite3_column_name(sqlite3_stmt*,int);
> > const void *sqlite3_column_name16(sqlite3_stmt*,int);
> >
> > The first parameter is a prepared SQL statement. This function returns
> > the column heading for the Nth column of that statement, where N is
> > the second function parameter. The string returned is UTF-8 for
> > sqlite3_column_name() and UTF-16 for sqlite3_column_name16().
>
> In other words, there is no need for the pragma.
>
> e
>
> > - Original Message - 
> > From: "Nuno Lucas" <[EMAIL PROTECTED]>
> > To: "sqlite" <[EMAIL PROTECTED]>
> > Sent: Monday, July 26, 2004 12:33 PM
> > Subject: Re: [sqlite] Versions 2.8.15 and 3.0.3 available
>
>
> >> D. Richard Hipp, dando pulos de alegria, escreveu :
> >> > The following pragmas are scheduled to be removed in the future:
> >> >
> >> > EMPTY_RESULT_CALLBACKS
> >> > FULL_COLUMN_NAMES
> >> > SHORT_COLUMN_NAMES
> >> > COUNT_CHANGES
> >> >
> >>
> >> What would be the equivalent to EMPTY_RESULT_CALLBACKS=TRUE then?
> >>
> >> I use it to get the column names list to display in a grid, even when
> >> the result is empty. I think it is better to the user to see them, even
> >> if no results are present.
> >>
> >> Regards,
> >> ~Nuno Lucas
> >>
> >>
>
>



Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-26 Thread Doug Currie

Monday, July 26, 2004, 12:33:41 PM, Roger Reghin wrote:

> I also use EMPTY_RESULT_CALLBACKS for the same reason Nuno does. And my
> software also needs FULL_COLUMN_NAMES as well. So, no 3.x for me... =(

In 3.x column names are available as soon as the query is prepared.
See the C API reference at
http://www.sqlite.org/capi3ref.html#sqlite3_column_name

> const char *sqlite3_column_name(sqlite3_stmt*,int);
> const void *sqlite3_column_name16(sqlite3_stmt*,int);
> 
> The first parameter is a prepared SQL statement. This function returns
> the column heading for the Nth column of that statement, where N is
> the second function parameter. The string returned is UTF-8 for
> sqlite3_column_name() and UTF-16 for sqlite3_column_name16().

In other words, there is no need for the pragma.

e

> - Original Message - 
> From: "Nuno Lucas" <[EMAIL PROTECTED]>
> To: "sqlite" <[EMAIL PROTECTED]>
> Sent: Monday, July 26, 2004 12:33 PM
> Subject: Re: [sqlite] Versions 2.8.15 and 3.0.3 available


>> D. Richard Hipp, dando pulos de alegria, escreveu :
>> > The following pragmas are scheduled to be removed in the future:
>> >
>> > EMPTY_RESULT_CALLBACKS
>> > FULL_COLUMN_NAMES
>> > SHORT_COLUMN_NAMES
>> > COUNT_CHANGES
>> >
>>
>> What would be the equivalent to EMPTY_RESULT_CALLBACKS=TRUE then?
>>
>> I use it to get the column names list to display in a grid, even when
>> the result is empty. I think it is better to the user to see them, even
>> if no results are present.
>>
>> Regards,
>> ~Nuno Lucas
>>
>>



Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-26 Thread Erwin Jabor
Hello Richard.

Please dont remove EMPTY_RESULT_CALLBACKS.
This will make it hard to continue with Callback.
It is a very nessessary part of Callback.
So please dont remove it.

Regards
Erwin Jabor





Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-26 Thread Roger Reghin \(Duty/Sedes/CWB\)
I also use EMPTY_RESULT_CALLBACKS for the same reason Nuno does. And my
software also needs FULL_COLUMN_NAMES as well. So, no 3.x for me... =(

Roger Reghin.


- Original Message - 
From: "Nuno Lucas" <[EMAIL PROTECTED]>
To: "sqlite" <[EMAIL PROTECTED]>
Sent: Monday, July 26, 2004 12:33 PM
Subject: Re: [sqlite] Versions 2.8.15 and 3.0.3 available


> D. Richard Hipp, dando pulos de alegria, escreveu :
> > The following pragmas are scheduled to be removed in the future:
> >
> > EMPTY_RESULT_CALLBACKS
> > FULL_COLUMN_NAMES
> > SHORT_COLUMN_NAMES
> > COUNT_CHANGES
> >
>
> What would be the equivalent to EMPTY_RESULT_CALLBACKS=TRUE then?
>
> I use it to get the column names list to display in a grid, even when
> the result is empty. I think it is better to the user to see them, even
> if no results are present.
>
> Regards,
> ~Nuno Lucas
>
>



Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-26 Thread Nuno Lucas
D. Richard Hipp, dando pulos de alegria, escreveu :
The following pragmas are scheduled to be removed in the future:
EMPTY_RESULT_CALLBACKS
FULL_COLUMN_NAMES
SHORT_COLUMN_NAMES
COUNT_CHANGES
What would be the equivalent to EMPTY_RESULT_CALLBACKS=TRUE then?
I use it to get the column names list to display in a grid, even when 
the result is empty. I think it is better to the user to see them, even 
if no results are present.

Regards,
~Nuno Lucas


Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-26 Thread D. Richard Hipp
CARIOTOGLOU MIKE wrote:
I noticed that the previous version had some PRAGMA's not implemented,
notably
DEFAULT_SYNCHRONOUS (and, I think, also SHOW_DATATYPES, or
EMPTY_RESULT_CALLBACKS, I am not sure).
any changes on this ?

DEFAULT_SYNCHRONOUS no longer exists.  The default setting for
synchronous is FULL.  If you want something different, you have
to change it every time you open a new connection.
SHOW_DATATYPES no longer exists.
The following pragmas are scheduled to be removed in the future:
EMPTY_RESULT_CALLBACKS
FULL_COLUMN_NAMES
SHORT_COLUMN_NAMES
COUNT_CHANGES

--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565


RE: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-26 Thread CARIOTOGLOU MIKE
I noticed that the previous version had some PRAGMA's not implemented,
notably
DEFAULT_SYNCHRONOUS (and, I think, also SHOW_DATATYPES, or
EMPTY_RESULT_CALLBACKS, I am not sure).
any changes on this ?



Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-23 Thread Roger Reghin \(Duty/Sedes/CWB\)
I'll try it and give you a feedback!!

Thank you so much! =)

Roger.


- Original Message - 
From: "Andy Colson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 22, 2004 9:56 PM
Subject: Re: [sqlite] Versions 2.8.15 and 3.0.3 available


> Roger Reghin (Duty/Sedes/CWB) wrote:
> > D. Hipp,
> >
> > is there a 2.8.15 pre-compiled DLL available??  I still couldn't find
any =(
> >
> > Thanks,
> >
> > Roger Reghin.
>
> I have compiled the 3.0.3 DLL as well as 2.8.15 (my first time with the
> 2.8.x so hopefully its right) and put them on my website:
>
> http://squeakycode.net/
>
> if anyone has problems please let me know.
>
> -Andy
>
> PS  I included the sqlite_encode_binary and decode_binary into the DLL,
> it just seemed like a good idea...  hope it wont break anything.
>



Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-22 Thread Andy Colson
Roger Reghin (Duty/Sedes/CWB) wrote:
D. Hipp,
is there a 2.8.15 pre-compiled DLL available??  I still couldn't find any =(
Thanks,
Roger Reghin.
I have compiled the 3.0.3 DLL as well as 2.8.15 (my first time with the 
2.8.x so hopefully its right) and put them on my website:

http://squeakycode.net/
if anyone has problems please let me know.
-Andy
PS  I included the sqlite_encode_binary and decode_binary into the DLL, 
it just seemed like a good idea...  hope it wont break anything.


Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-22 Thread D. Richard Hipp
Matt Sergeant wrote:
On Thu, 22 Jul 2004, D. Richard Hipp wrote:

Two new versions of SQLite are available on the website.
See the news column on the right for details.
   http://www.sqlite.org/

Did 3.0.3 have a very negative effect on create/drop table speed? I have a 
benchmark in the DBD::SQLite test suite that has suddenly dropped off the 
chart in speed terms.

Below a speed comparison betwen 3.0.1 and 3.0.3 for creating and
droping 500 tables with multiple indices.  3.0.3 is a little faster.
Test 1: 500 CREATE TABLES, CREATE INDEXes, and INSERTs
 BEGIN
 CREATE TABLE t1(a,b UNIQUE, c PRIMARY KEY);
 CREATE INDEX i1 ON t1(a);
 ... 1496 lines omitted
 CREATE INDEX i500 ON t500(a);
 INSERT INTO t500 VALUES(1,2,3);
 COMMIT
   sqlite301a 2004-Jun-25 13.455 2114KB
   sqlite303a 2004-Jul-22 12.484 2114KB
Test 2: 500 DROPs
 BEGIN
 DROP TABLE t1;
 DROP TABLE t2;
 ... 496 lines omitted
 DROP TABLE t499;
 DROP TABLE t500;
 COMMIT
   sqlite301a 2004-Jun-25 4.483 2114KB
   sqlite303a 2004-Jul-22 4.372 2114KB

--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565


Re: [sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-22 Thread Roger Reghin \(Duty/Sedes/CWB\)
D. Hipp,

is there a 2.8.15 pre-compiled DLL available??  I still couldn't find any =(

Thanks,

Roger Reghin.



- Original Message - 
From: "D. Richard Hipp" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 22, 2004 4:10 PM
Subject: [sqlite] Versions 2.8.15 and 3.0.3 available


> Two new versions of SQLite are available on the website.
> See the news column on the right for details.
>
> http://www.sqlite.org/
>
> -- 
> D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
>
>



[sqlite] Versions 2.8.15 and 3.0.3 available

2004-07-22 Thread D. Richard Hipp
Two new versions of SQLite are available on the website.
See the news column on the right for details.
   http://www.sqlite.org/
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565