RE: [sqlite] bug in sqlite 3.2.5 compilation and ANALYZE

2005-09-06 Thread Cariotoglou Mike
ok, I pinned it down. it is a genuine bug, and has nothing to do with
dlls and wrappers.

to reproduce, do this:

1. open the command-line utility on a database (or even with no
database, it does not matter)
2. type this:


SQLite version 3.2.5
Enter ".help" for instructions
sqlite> pragma empty_Result_callbacks=1;
sqlite> analyze; 

this will crash immediately. 
in general, if empty_Result_callbacks is set, AND the database is
analyzed, sqlite crashes consistently. 

the reason it appeared in sqlite3Explorer is that it sets the pragma by
default.

DRH, pls check this.

> -Original Message-
> From: Miha Vrhovnik [mailto:[EMAIL PROTECTED] 
> Sent: Monday, September 05, 2005 7:14 PM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] bug in sqlite 3.2.5 compilation and ANALYZE
> 
> "Cariotoglou Mike" <[EMAIL PROTECTED]> je ob 5.9.2005 
> 14:49:54 napisal(a):
> 
> >ok.
> >I use sqlite3Explorer (which should not matter), I create a new 
> >database, then I run :
> >
> >create table test1(id integer);
> >analyze
> >
> >this crashes immediately, with dll 3.2.5. it works fine from the 
> >command-line.
> > 
> I can confirm that. But it seems that the problem is in 
> Sqlite explorer or your sqlite3.dll wrapper implementation. 
> When I try that with my own Delphi wrapper implementation it 
> works. But opening database with sqlite explorer results in crash.
> 
> Regards,
> Miha
> 
> 
> 



RE: [sqlite] bug in sqlite 3.2.5 compilation and ANALYZE

2005-09-05 Thread Cariotoglou Mike
ok.
I use sqlite3Explorer (which should not matter), I create a new
database, then I run :

create table test1(id integer);
analyze

this crashes immediately, with dll 3.2.5. it works fine from the
command-line.
 

> -Original Message-
> From: Ned Batchelder [mailto:[EMAIL PROTECTED] 
> Sent: Monday, September 05, 2005 3:10 PM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] bug in sqlite 3.2.5 compilation and ANALYZE
> 
> Perhaps you could provide the exact SQL that crashed.  The 
> code seems to be very well tested automatically, so it is 
> very unlikely that all ANALYZE executions fail.
> 
> --Ned.
> http://nedbatchelder.com
>  
> -Original Message-
> From: Cariotoglou Mike [mailto:[EMAIL PROTECTED]
> Sent: Monday, 05 September, 2005 5:46 AM
> To: sqlite-users@sqlite.org
> Subject: [sqlite] bug in sqlite 3.2.5 compilation and ANALYZE
> 
> I tried the ANALYZE statement with sqlite 3.2.5 in dll form, 
> (both the pre-compiled version downloaded from the site, AND 
> a local compilation).
> in both
> cases, the statement fails with an ACCESS VIOLATION. however, 
> the same statement, when run from the pre-compiled 
> sqlite3.exe, works. 
> further, having succesfully ANALYZED a database with the 
> command-line program, I can no longer work with the database 
> using the DLL api. 
> I think there is something very wrong with the compilation 
> defines of the DLL. 
> 
> DRH: can you pls check and fix ?
> ALL: can you verify that the DLL API crashes on ANALYZE ? (WINDOWS,
> obviously)
> 
> 
> 
> 
> 
> 
> 



RE: [sqlite] bug in sqlite 3.2.5 compilation and ANALYZE

2005-09-05 Thread Ned Batchelder
Perhaps you could provide the exact SQL that crashed.  The code seems to be
very well tested automatically, so it is very unlikely that all ANALYZE
executions fail.

--Ned.
http://nedbatchelder.com
 
-Original Message-
From: Cariotoglou Mike [mailto:[EMAIL PROTECTED] 
Sent: Monday, 05 September, 2005 5:46 AM
To: sqlite-users@sqlite.org
Subject: [sqlite] bug in sqlite 3.2.5 compilation and ANALYZE

I tried the ANALYZE statement with sqlite 3.2.5 in dll form, (both the
pre-compiled version downloaded from the site, AND a local compilation).
in both
cases, the statement fails with an ACCESS VIOLATION. however, the same
statement, when run from the pre-compiled sqlite3.exe, works. 
further, having succesfully ANALYZED a database with the command-line
program, I can no longer work with the database using the DLL api. 
I think there is something very wrong with the compilation defines of
the DLL. 

DRH: can you pls check and fix ?
ALL: can you verify that the DLL API crashes on ANALYZE ? (WINDOWS,
obviously)