[sqlite] Test

[Iulian Onofrei]

test


iulianOnofrei

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Test failures on GPFS

[T J]

On Sunday, January 12, 2020, Roman Fleysher 
wrote:

>
> I use SQLite over GPFS , but in DELETE (which I think is the default)
> mode. Not WAL mode. No issues with locking, except performance when
> accessing concurrently from multiple nodes. As others pointed out, this has
> to do with the overhead due to lock requests. GPFS must coordinate with
> many nodes. My observation is that when concurrent access is from a few
> nodes, the performance is OK even though number of nodes is always the
> same. Thus, GPFS coordinates in some smart way only between nodes actively
> involved.
>
> One reason I do not use mySQL with its more efficient network access is
> that sys admin must set it up. With SQLite, I am independent. In addition,
> in my SQL there are authentication issues to be dealt with. I rely on GPFS
> file access permissions (access control list, ACL) to regulate access to
> database.
>
> I heard about BeadrockDB, which internally uses SQLite and provides
> network access with replication. I have not tried it and do not know what
> is involved.
>
>
>
MySQL and similar would indeed be nice to use, but in addition to the
administrative cost, there are also developer costs to get things set up so
that every developer can do work in their own db without affecting the
production db, as well as complexity costs with getting data into those
dbs. Contrast this with just copying the sqlite file(s) as needed (though
integrity concerns still exist).

So I'm mostly weighing options. The data is very much many-reads,
few-writes. Also considering just using an external locking service and
simple flat files, but this has obvious downsides of fewer (if any) data
types, no joins, no transactions, etc.

I may give this a try and see if the perf hit is tolerable.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test failures on GPFS

[Roman Fleysher]

I use SQLite over GPFS , but in DELETE (which I think is the default) mode. Not 
WAL mode. No issues with locking, except performance when accessing 
concurrently from multiple nodes. As others pointed out, this has to do with 
the overhead due to lock requests. GPFS must coordinate with many nodes. My 
observation is that when concurrent access is from a few nodes, the performance 
is OK even though number of nodes is always the same. Thus, GPFS coordinates in 
some smart way only between nodes actively involved.

One reason I do not use mySQL with its more efficient network access is that 
sys admin must set it up. With SQLite, I am independent. In addition, in my SQL 
there are authentication issues to be dealt with. I rely on GPFS file access 
permissions (access control list, ACL) to regulate access to database.

I heard about BeadrockDB, which internally uses SQLite and provides network 
access with replication. I have not tried it and do not know what is involved.


Roman



From: sqlite-users  on behalf of 
Richard Hipp 
Sent: Saturday, January 11, 2020 8:59 PM
To: SQLite mailing list 
Subject: Re: [sqlite] Test failures on GPFS

CAUTION: This email comes from an external source; the attachments and/or links 
may compromise our secure environment. Do not open or click on suspicious 
emails. Please click on the “Phish Alert” button on the top right of the 
Outlook dashboard to report any suspicious emails.

On 1/11/20, J. King  wrote:
>
> WAL mode does not work over the network, so the test failures are presumably
> to be expected.
>

WAL mode should work on a network filesystem, as long as all of the
clients are on the same host computer, and as long as mmap()-ing the
*-shm file gives all the clients shared memory.  Dunno if GPFS does
that or not, though.  Maybe not.  Or, maybe not reliably.

--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmailinglists.sqlite.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsqlite-usersdata=02%7C01%7Croman.fleysher%40einsteinmed.org%7Cba1544a0f3584e8a077008d7970309d8%7C9c01f0fd65e040c089a82dfd51e62025%7C0%7C1%7C637143911624961155sdata=udLAzknx7zL4yHzQk8ZPQI8mAWltFusqvcb%2FW31XuaY%3Dreserved=0
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test failures on GPFS

[Richard Hipp]

On 1/11/20, J. King  wrote:
>
> WAL mode does not work over the network, so the test failures are presumably
> to be expected.
>

WAL mode should work on a network filesystem, as long as all of the
clients are on the same host computer, and as long as mmap()-ing the
*-shm file gives all the clients shared memory.  Dunno if GPFS does
that or not, though.  Maybe not.  Or, maybe not reliably.

-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test failures on GPFS

[J. King]

On January 11, 2020 5:57:31 p.m. EST, T J  wrote:

>I was interested in using sqlite over GPFS.  I've seen a few useful
>threads
>on this:
>
> [...]
>
>Overall, it looks pretty good, but there were some WAL
>failures.
>Could someone comment on the precise implication of those test
>failures?

WAL mode does not work over the network, so the test failures are presumably to 
be expected. 

-- 
J. King
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test failures on GPFS

[Jens Alfke]

> On Jan 11, 2020, at 2:58 PM, T J  wrote:
> 
> I was interested in using sqlite over GPFS.

The standard advice on using SQLite over a network file system is “don’t do 
it.” Even if you find the rare file system that handles locks properly, you’ll 
likely have performance issues.

A client/server database like Postgres or MySQL is a better fit for a 
distributed use case. If you’re sending everything over the network, it makes 
more sense to send just the queries & results, not the innards of the b-tree 
too. Is there a reason you can’t use one of those?

—Jens
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Test failures on GPFS

[T J]

Hi,

I was interested in using sqlite over GPFS.  I've seen a few useful threads
on this:

   - Network file system that support sqlite3 well

   
https://www.mail-archive.com/sqlite-users@mailinglists.sqlite.org/msg117085.html

   - disable file locking mechanism over the network

   
https://www.mail-archive.com/sqlite-users@mailinglists.sqlite.org/msg116846.html

From these, I can see that there are some performance issues, even if I
willing (which I am not) to make all access (read+write) sequential. [I
don't expect to need many, if any, concurrent writers, but I will typically
have concurrent readers.]

To get a better sense of things, I downloaded 3.31.0 and ran the test suite
on GPFS.  Overall, it looks pretty good, but there were some WAL failures.
Could someone comment on the precise implication of those test failures?
I'm interested to know what usage patterns are likely to cause problems,
and which are likely safe.  Also, which other tests can I run (
https://www.sqlite.org/testing.html)? Perhaps more tests around concurrent
read/writes?

!Failures on these tests: e_walauto-1.1.2 e_walauto-1.1.3
e_walauto-1.1.5 e_walauto-1.1.7 e_walauto-1.1.12.3 e_walauto-1.1.12.5
e_walauto-1.2.2 e_walauto-1.2.3 e_walauto-1.2.5 e_walauto-1.2.7
e_walauto-1.2.12.3 e_walauto-1.2.12.5 zipfile-2.4a.2.1
zipfile-2.4a.2.2


Thanks in advance.  The `make test` output log snippet is below.
---

e_walauto-1.1.0... Ok

e_walauto-1.1.1... Ok

e_walauto-1.1.2...

! e_walauto-1.1.2 expected: [1]

! e_walauto-1.1.2 got:  [0]

e_walauto-1.1.3...

! e_walauto-1.1.3 expected: [1]

! e_walauto-1.1.3 got:  [0]

e_walauto-1.1.4... Ok

e_walauto-1.1.5...

! e_walauto-1.1.5 expected: [1]

! e_walauto-1.1.5 got:  [0]

e_walauto-1.1.6... Ok

e_walauto-1.1.7...

! e_walauto-1.1.7 expected: [1]

! e_walauto-1.1.7 got:  [0]

e_walauto-1.1.7... Ok

e_walauto-1.1.8... Ok

e_walauto-1.1.9... Ok

e_walauto-1.1.10.1... Ok

e_walauto-1.1.10.2... Ok

e_walauto-1.1.11.1... Ok

e_walauto-1.1.11.2... Ok

e_walauto-1.1.11.3... Ok

e_walauto-1.1.12.1... Ok

e_walauto-1.1.12.2... Ok

e_walauto-1.1.12.3...

! e_walauto-1.1.12.3 expected: [2]

! e_walauto-1.1.12.3 got:  [0]

e_walauto-1.1.12.4... Ok

e_walauto-1.1.12.5...

! e_walauto-1.1.12.5 expected: [1559]

! e_walauto-1.1.12.5 got:  [0]

e_walauto-1.2.0... Ok

e_walauto-1.2.1... Ok

e_walauto-1.2.2...

! e_walauto-1.2.2 expected: [1]

! e_walauto-1.2.2 got:  [0]

e_walauto-1.2.3...

! e_walauto-1.2.3 expected: [1]

! e_walauto-1.2.3 got:  [0]

e_walauto-1.2.4... Ok

e_walauto-1.2.5...

! e_walauto-1.2.5 expected: [1]

! e_walauto-1.2.5 got:  [0]

e_walauto-1.2.6... Ok

e_walauto-1.2.7...

! e_walauto-1.2.7 expected: [1]

! e_walauto-1.2.7 got:  [0]

e_walauto-1.2.7... Ok

e_walauto-1.2.8... Ok

e_walauto-1.2.9... Ok

e_walauto-1.2.10.1... Ok

e_walauto-1.2.10.2... Ok

e_walauto-1.2.11.1... Ok

e_walauto-1.2.11.2... Ok

e_walauto-1.2.11.3... Ok

e_walauto-1.2.12.1... Ok

e_walauto-1.2.12.2... Ok

e_walauto-1.2.12.3...

! e_walauto-1.2.12.3 expected: [2]

! e_walauto-1.2.12.3 got:  [0]

e_walauto-1.2.12.4... Ok

e_walauto-1.2.12.5...

! e_walauto-1.2.12.5 expected: [1559]

! e_walauto-1.2.12.5 got:  [0]

e_walauto.test-closeallfiles... Ok

e_walauto.test-sharedcachesetting... Ok

Time: e_walauto.test 92703 ms

...

zipfile2.test-closeallfiles... Ok

zipfile2.test-sharedcachesetting... Ok

Time: zipfile2.test 14 ms

Memory used:  now 24  max9283664  max-size   16908288

Allocation count: now  1  max1311131

Page-cache used:  now  0  max 13  max-size  65800

Page-cache overflow:  now  0  max   20640016

SQLite 2020-01-10 01:05:49
0a500da6aa659a8e73206e6d22ddbf2da5e4f1d1d551eeb66433163a3e13109d

14 errors out of 249964 tests on localhost Linux 64-bit little-endian

!Failures on these tests: e_walauto-1.1.2 e_walauto-1.1.3
e_walauto-1.1.5 e_walauto-1.1.7 e_walauto-1.1.12.3 e_walauto-1.1.12.5
e_walauto-1.2.2 e_walauto-1.2.3 e_walauto-1.2.5 e_walauto-1.2.7
e_walauto-1.2.12.3 e_walauto-1.2.12.5 zipfile-2.4a.2.1
zipfile-2.4a.2.2

All memory allocations freed - no leaks

Memory used:  now  0  max9283664  max-size   16908288

Allocation count: now  0  max1311131

Page-cache used:  now  0  max 13  max-size  65800

Page-cache overflow:  now  0  max   20640016

Maximum memory usage: 9283664 bytes

Current memory usage: 0 bytes

Number of malloc()  : -1 calls
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Two Sqlite test cases fail - sqlite-src-3280000

[Frederik Wedel-Heinen]

Hi,

I want to run the Sqlite tests inside a docker in order to run tests easily on 
any platform. Please let me know if you have bad experiences with Docker.
I experience two test cases fail:

sqlite-make-test_1  | ! oserror-1.4.1 expected: [1 {unable to open database 
file}]
sqlite-make-test_1  | ! oserror-1.4.1 got:  [0 {}]
sqlite-make-test_1  | ! oserror-1.4.2 expected: [^os_unix.c:\d*: \(\d+\) 
(open|readlink|lstat)\(.*test.db\) - ]
sqlite-make-test_1  | ! oserror-1.4.2 got:  []

I have created a Dockerfile (which configures the docker image build) and a 
Docker Compose file (that describes how the tests are run).
Assuming you have Docker installed you should be able to run “the testing 
service” by placing the two files in a subdirectory to the Sqlite3 root folder 
and executing from a command line:

"docker-compose -f docker-compose_maketest.yml up” (Shall be run from the 
subdirectory)

The tests will now run (Notice that they do not run fast). The repository must 
be “make distclean”’ed before running the Docker.

Regards,
Frederik
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test error in oserror-2.1.1

[Free Ekanayaka]

Hi,

Dan Kennedy  writes:

> On 02/19/2018 01:28 AM, Free Ekanayaka wrote:
>> Hello,
>>
>> I've tried to run the quicktest suite for SQLite 3.22.0 on Linux (kernel
>> version 4.13.0), and when it executes test/oserror.test I get errors:
>>
>> oserror-1.1.1... Ok
>> oserror-1.1.2... Ok
>> oserror-1.1.3... Ok
>> oserror-1.2.1... Ok
>> oserror-1.2.2... Ok
>> oserror-1.3.1... Ok
>> oserror-1.3.2... Ok
>> oserror-1.4.1... Ok
>> oserror-1.4.2... Ok
>> oserror-2.1.1...
>> ! oserror-2.1.1 expected: [1 {disk I/O error}]
>> ! oserror-2.1.1 got:  [0 {}]
>> oserror-2.1.2...
>> ! oserror-2.1.2 expected: [^os_unix.c:\d+: \(\d+\) unlink\(.*test.db-wal\) - 
>> ]
>> ! oserror-2.1.2 got:  []
>> oserror-2.1.3... Ok
>>
>> After looking at the code in test/oserror.test, I'm confused about how
>> it could possibly ever pass: as far as I can see and understand, it does
>> not enable WAL journaling at all:
>
> When SQLite opens a read or write transaction on a database file zero 
> bytes in size, it attempts to delete any journal or wal file that is 
> already present in the file system using unlink() before proceeding. And 
> any unlink() on a directory should fail with EISDIR, causing the errors 
> that the test cases are looking for.
>
> Not sure what is going wrong here though. If you try the same test with 
> the shell tool:
>
>$ rm -f x.db
>$ mkdir x.db-wal
>$ sqlite3 x.db
>...
>sqlite> select * from sqlite_master;
>Error: disk I/O error
>
> do you get the I/O error/

I believe I found the issue. Apparently if you're using btrfs as file
system, the above error does not occur. I didn't yet investigate why,
but that's what I get from testing it.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test error in oserror-2.1.1

[Dan Kennedy]

On 02/19/2018 01:28 AM, Free Ekanayaka wrote:

Hello,

I've tried to run the quicktest suite for SQLite 3.22.0 on Linux (kernel
version 4.13.0), and when it executes test/oserror.test I get errors:

oserror-1.1.1... Ok
oserror-1.1.2... Ok
oserror-1.1.3... Ok
oserror-1.2.1... Ok
oserror-1.2.2... Ok
oserror-1.3.1... Ok
oserror-1.3.2... Ok
oserror-1.4.1... Ok
oserror-1.4.2... Ok
oserror-2.1.1...
! oserror-2.1.1 expected: [1 {disk I/O error}]
! oserror-2.1.1 got:  [0 {}]
oserror-2.1.2...
! oserror-2.1.2 expected: [^os_unix.c:\d+: \(\d+\) unlink\(.*test.db-wal\) - ]
! oserror-2.1.2 got:  []
oserror-2.1.3... Ok

After looking at the code in test/oserror.test, I'm confused about how
it could possibly ever pass: as far as I can see and understand, it does
not enable WAL journaling at all:


When SQLite opens a read or write transaction on a database file zero 
bytes in size, it attempts to delete any journal or wal file that is 
already present in the file system using unlink() before proceeding. And 
any unlink() on a directory should fail with EISDIR, causing the errors 
that the test cases are looking for.


Not sure what is going wrong here though. If you try the same test with 
the shell tool:


  $ rm -f x.db
  $ mkdir x.db-wal
  $ sqlite3 x.db
  ...
  sqlite> select * from sqlite_master;
  Error: disk I/O error

do you get the I/O error/

Dan.






ifcapable wal {
   do_test 2.1.1 {
 set ::log [list]
 file mkdir test.db-wal
 forcedelete test.db
 list [catch {
   sqlite3 dbh test.db
   execsql { SELECT * FROM sqlite_master } dbh
 } msg] $msg
   } {1 {disk I/O error}}
   
   do_re_test 2.1.2 {

 lindex $::log 0
   } {^os_unix.c:\d+: \(\d+\) unlink\(.*test.db-wal\) - }
   do_test 2.1.3 {
 catch { dbh close }
 forcedelete test.db-wal
   } {}
}

so the file "testdir/test.db-wal" (which the test overrides with a dir)
does never come into play in the testdir/test.db DB that the test opens.

On the contrary, other WAL-related tests (such as test/wal.test) do
enable WAL journaling via "PRAGMA journal_mode = wal".

Any hints?

Thanks
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users



___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Test error in oserror-2.1.1

[Free Ekanayaka]

Hello,

I've tried to run the quicktest suite for SQLite 3.22.0 on Linux (kernel
version 4.13.0), and when it executes test/oserror.test I get errors:

oserror-1.1.1... Ok
oserror-1.1.2... Ok
oserror-1.1.3... Ok
oserror-1.2.1... Ok
oserror-1.2.2... Ok
oserror-1.3.1... Ok
oserror-1.3.2... Ok
oserror-1.4.1... Ok
oserror-1.4.2... Ok
oserror-2.1.1...
! oserror-2.1.1 expected: [1 {disk I/O error}]
! oserror-2.1.1 got:  [0 {}]
oserror-2.1.2...
! oserror-2.1.2 expected: [^os_unix.c:\d+: \(\d+\) unlink\(.*test.db-wal\) - ]
! oserror-2.1.2 got:  []
oserror-2.1.3... Ok

After looking at the code in test/oserror.test, I'm confused about how
it could possibly ever pass: as far as I can see and understand, it does
not enable WAL journaling at all:

ifcapable wal {
  do_test 2.1.1 {
set ::log [list]
file mkdir test.db-wal
forcedelete test.db
list [catch {
  sqlite3 dbh test.db
  execsql { SELECT * FROM sqlite_master } dbh
} msg] $msg
  } {1 {disk I/O error}}
  
  do_re_test 2.1.2 { 
lindex $::log 0 
  } {^os_unix.c:\d+: \(\d+\) unlink\(.*test.db-wal\) - }
  do_test 2.1.3 { 
catch { dbh close }
forcedelete test.db-wal
  } {}
}

so the file "testdir/test.db-wal" (which the test overrides with a dir)
does never come into play in the testdir/test.db DB that the test opens.

On the contrary, other WAL-related tests (such as test/wal.test) do
enable WAL journaling via "PRAGMA journal_mode = wal".

Any hints?

Thanks
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] About test_vfs.c in sqlite test

[Nick]

I find a file named test_vfs.c when I run the tcl tests in the source tree.
When I open a wal-file with a sqlite3_file* file descriptor pFile1, it
called sqlite3OsOpen(). The call tree is like the pic below:

sqlite3OsOpen(pFile1)
  |
  |
 pVfs->xOpen ==> tvfsOpen
  |
  |
 sqlite3OsOpen(pFile2)
  |
  |
  pVfs->xOpen ==> unixOpen(pFile2)

In some tests, test_vfs.c is involved and pVfs->xOpen() will bind to
tvfsOpen() instead of unixOpen() directly. 
And I find the address of pFile has changed to pFile2 when sqlite3OsOpen()
is called in the second time. 
Then unixOpen will initialize pFile2, such as set nFetchOut and some other
member elements in struct unixFile to 0. But the nFetchOut of pFile1 may not
be 0 when sqlite3OsOpen(pFile1) returns.

It makes me confused as I find db will not crash even if all the member
elements of the unixFile is not correct. Could it be said that these
elements will not be used before they are set to a right value?
And what is test_vfs.c for?

I am new bee to sqlite test and vfs. Could anyone explain me it is correct
that the nFetchOut of pFile1 is not 0 when sqlite3OsOpen(pFile1) returns? 

I am really confused. Thanks for any light you can shed. 



--
Sent from: http://sqlite.1065341.n5.nabble.com/
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Test failures ftsconf3.[1-68] on HPPA and Sparc

[Rolf Eike Beer]

Greetings,

for at least 3.17.0 to 3.20.1 most ftsconf tests fail on Sparc. I've also 
verified it with 3.20.1 on HPPA, so it is not machine dependend.

The output of the tests (all look the same, so only first one here) look 
suspiciously like an endianess issue (both HPPA and Sparc are big endian):

! fts3conf-3.1 expected: [X'01000200']
! fts3conf-3.1 got:  [X'00010002']

Also tracked here:

https://bugs.gentoo.org/show_bug.cgi?id=630818

Greetings,

Eike

signature.asc
Description: This is a digitally signed message part.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] TEST: please ignore and delete

[Winfried]

I'm just checking that the list is again reachable from Nabble after an admin
changed the mail address from @sqlite.org to @mailinglists.sqlite.org

http://sqlite.1065341.n5.nabble.com/

Admins: If need be, please delete this message later.



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/TEST-please-ignore-and-delete-tp96561.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Test "vtabH.test" fails when first dir of the path contains underscore

[Emanuele Di Giacomo]

Hi,
test "vtabH.test" fails when executed in a path were the first
directory contains an underscore (e.g "/p_ath/to" or "/h_ome/test/"):

$ pwd
/h_ome/test/sqlite-src-3190200

$ ./configure && make && make test
...
Time: vtabE.test 11 ms
Time: vtabF.test 12 ms
! vtabH-3.6 expected:
[/h_ome/test/sqlite-src-3190200/testdir/subdir/x1.txt 143
/h_ome/test/sqlite-src-3190200/testdir/subdir/x2.txt 153]
! vtabH-3.6 got:  []
! vtabH-3.7 expected: [296]
! vtabH-3.7 got:  [{}]
Time: vtabH.test 365 ms
Time: vtabI.test 14 ms
...

Best regards,

   Emanuele
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] how to run the SQLite test suite ?

[Richard Hipp]

On 5/10/17, Jason Vas Dias  wrote:
>
> Now I would like run some some 'test suite' that will allow me to
> determine if the build is OK - but there appears to be none :
>

As Simon already pointed out, you have download the pre-compiled
"amalgamation" sources.  That tarball does not include any tests, in
as much as the source code to the amalgamation has already been
thoroughly tested.

The TCL tests are available in the canonical source tree at
https://sqlite.org/src

The SQLLOGICTEST suite is available in a separate repository at
https://sqlite.org/sqllogictest

Both of the test suites above are designed to test the source code,
not machine code. By this I mean that both of the test suites above
compile SQLite separately and either build SQLite into a test
application, or use non-standard compile-time options to facilitate
testing.  Machine code is generated for the test suites above, but it
is not exactly the same machine code that will be generated for your
application.  The tests above are very powerful for verifying the
correctness of the SQLite source code, but since they are not "fly
what you test and test what you fly" they do not qualify as tests for
the generated machine code.  In other words, the test suites above
assume there are no bugs in your C compiler.

The source code in "sqlite3.c" has already been thoroughly tested for
you.  So if you trust your compiler to correctly convert C source code
into machine code, no further testing should be necessary.

If you do not trust your compiler and/or you want to independently
verify that the generated machine code you are actually shipping is
correct, that requires the TH3 test suite, which is not open source.

Note that most people explicitly trust their C compilers.  In fact,
both Apple and Google do their own builds of SQLite for MacOS/iOS and
Android that use the SQLITE_UNTESTABLE
(https://www.sqlite.org/compile.html#untestable) compile-time option,
thereby preventing you from completely testing the machine code even
if you wanted to and have access to TH3.

-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] how to run the SQLite test suite ?

[Simon Slavin]

On 10 May 2017, at 2:26pm, Jason Vas Dias  wrote:

> I just downloaded & built sqlite-autoconf-318 on Linux x86_64 .
> 
> Now I would like run some some 'test suite' that will allow me to
> determine if the build is OK - but there appears to be none :

What you have there is the amalgamation source code: just enough source code to 
be able to include SQLite in your programming projects.  The one you want is 
the complete source tree at the bottom of the page, under the heading 
_Alternative Source Code Formats_.

Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] how to run the SQLite test suite ?

[Jason Vas Dias]

Good day -

I just downloaded & built sqlite-autoconf-318 on Linux x86_64 .

Now I would like run some some 'test suite' that will allow me to
determine if the build is OK - but there appears to be none :

$ make check
make: Nothing to be done for 'check'.

(no test runs are done - this appears to be an alias for 'check-am', to check
 that automake generation succeeeded) .

$ make test
make: *** No rule to make target 'test'.  Stop.

In SQLite source directory:
$   find . -iname '*test*'
$
There is no SQLite source file with the word 'Test' in the name, ignoring case .


You have put up a page on the web called 'How SQLite is Tested' :
https://sqlite.org/testing.html

But no-where on that page is described 'How to Test SQLite'  ,
nor are there any links to the test-suite source code, which
evidently is not shipped in the SQLite source code, but which
apparently exists, since the page states:
" As of version 3.16.2 (2017-01-06), the SQLite library consists of
approximately
  122.9 KSLOC of C code. (KSLOC means thousands of "Source Lines Of Code" or,
  in other words, lines of code excluding blank lines and comments.) By
  comparison, the project has 745 times as much test code and test
scripts - 91596.1
  KSLOC.
" .

Where is this 91596.1 KSLOC of test code ?

It does not appear to be shipped with SQLite .

How do I run the tests ?

There appears to be no documentation for this
online or in the source tarball .

Thanks & Regards,
Jason
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test

[Stayros Mpampis]

?

[sqlite] test

[Stayros Mpampis]

eyax

[sqlite] Test

[Mike Owens]

This is a test. The sqlite-users at sqlite.org address has been blocked.
Only sqlite-users at mailinglists.sqlite.org should be allowed through.

Mike

[sqlite] test for bounce detection

[R.Smith]

On 2/14/2015 10:18 AM, Ma?l Nison wrote:
> As a side, it's the first time that I received a mail from this mailing
> list without it being automatically flagged as spam.

Well, technically this is spam... but it's the good kind :)

Thank you kindly Mike for the prompt repair and keeping things running 
smoothly - much appreciated!

[sqlite] test for bounce detection

[Maël Nison]

As a side, it's the first time that I received a mail from this mailing
list without it being automatically flagged as spam.

Le sam. 14 f?vr. 2015 06:26, Simon Slavin  a ?crit :

> On 14 Feb 2015, at 4:25am, Mike Owens  wrote:
>
> > So I updated mailman today to use mailinglists.sqlite.org rather than
> > sqlite.org:8080 knowing that there is a good chance some issues will
> arise.
> > I have been fixing them as they surface. This issue is related to the
> > Postfix config not recognizing mailinglists.sqlite.org. I've updated it
> an
> > restarted postfix so this should in theory fix it.
>
> This reply was sent to General Discussion of SQLite Database <
> sqlite-users at mailinglists.sqlite.org> so if it appears the problem has
> been fixed.  Thanks for the work, Mike.  Not just today, but for everything
> you do to keep the list working.
>
> Simon.
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] test for bounce detection

[Stephen Chrzanowski]

GMail has constantly and randomly flagged different messages from this
mailing list as spam.  I set a specific mail rule to force the mail to NOT
be flagged as spam.  The nice thing is, GMail also tells me when the
message SHOULD have been put into spam but because of my mail rule, the
message ended up where I'm looking at it.  We'll see how many more flags I
get. :]

On Sat, Feb 14, 2015 at 3:18 AM, Ma?l Nison  wrote:

> As a side, it's the first time that I received a mail from this mailing
> list without it being automatically flagged as spam.
>
> Le sam. 14 f?vr. 2015 06:26, Simon Slavin  a ?crit :
>
> > On 14 Feb 2015, at 4:25am, Mike Owens  wrote:
> >
> > > So I updated mailman today to use mailinglists.sqlite.org rather than
> > > sqlite.org:8080 knowing that there is a good chance some issues will
> > arise.
> > > I have been fixing them as they surface. This issue is related to the
> > > Postfix config not recognizing mailinglists.sqlite.org. I've updated
> it
> > an
> > > restarted postfix so this should in theory fix it.
> >
> > This reply was sent to General Discussion of SQLite Database <
> > sqlite-users at mailinglists.sqlite.org> so if it appears the problem has
> > been fixed.  Thanks for the work, Mike.  Not just today, but for
> everything
> > you do to keep the list working.
> >
> > Simon.
> > ___
> > sqlite-users mailing list
> > sqlite-users at mailinglists.sqlite.org
> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] test for bounce detection

[Simon Slavin]

On 14 Feb 2015, at 4:25am, Mike Owens  wrote:

> So I updated mailman today to use mailinglists.sqlite.org rather than
> sqlite.org:8080 knowing that there is a good chance some issues will arise.
> I have been fixing them as they surface. This issue is related to the
> Postfix config not recognizing mailinglists.sqlite.org. I've updated it an
> restarted postfix so this should in theory fix it.

This reply was sent to General Discussion of SQLite Database  so if it appears the problem has been fixed.  Thanks 
for the work, Mike.  Not just today, but for everything you do to keep the list 
working.

Simon.

[sqlite] test for bounce detection

[R.Smith]

I can confirm the bounces happen for the ".mailinglists" email address 
which is now automatically added to the "Reply-To" address.

I hit the reply-to-all button and then remove the .mailinglists address 
to fix it, but it is rather cumbersome, if the powers that control such 
things could kindly adjust that setting it will be most appreciated.


On 2/14/2015 2:04 AM, Simon Slavin wrote:
> On 13 Feb 2015, at 11:39pm, David King  wrote:
>
>> Maybe unrelated, but in the last few hours the list ID header changed from 
>> "sqlite-users.sqlite.org" to "sqlite-users.mailinglists.sqlite.org", which 
>> messes up my mail filtering.
> Thanks, David.  That was it.
>
> For others: messages from the list now reach me with a 'From' header which 
> includes 'mailinglists.'.  So when I hit 'reply' that's the address my 
> message goes to.  Whereas when I start a new thread my mailer uses the 
> address in my contact list which is the proper address.
>
> Thanks to David for helping me figure that out so quickly.  I hand-edited the 
> 'To' header on this message and I expect it'll go through.
>
> Simon.
>

[sqlite] test for bounce detection

[Simon Slavin]

On 13 Feb 2015, at 11:39pm, David King  wrote:

> Maybe unrelated, but in the last few hours the list ID header changed from 
> "sqlite-users.sqlite.org" to "sqlite-users.mailinglists.sqlite.org", which 
> messes up my mail filtering.

Thanks, David.  That was it.  

For others: messages from the list now reach me with a 'From' header which 
includes 'mailinglists.'.  So when I hit 'reply' that's the address my message 
goes to.  Whereas when I start a new thread my mailer uses the address in my 
contact list which is the proper address.

Thanks to David for helping me figure that out so quickly.  I hand-edited the 
'To' header on this message and I expect it'll go through.

Simon.

[sqlite] test for bounce detection

[Simon Slavin]

This is a test message.  I just sent another message to the list and it got 
bounced with the message "Relay access denied" so I want to see if this one 
made it.

If it does, can the listadmin see if there's anything wrong ?  Sorry to occupy 
your Friday night or weekend.

Simon.

[sqlite] test for bounce detection

[Mike Owens]

We are in the process of moving mailman from sqlite.org:8080 to
mailinglists.sqlite.org. The reason for this is that sqlite.org runs on a
different web server (althttpd) than the mailman management (Apache) and so
we originally used port 8080 for mailman. Well, port 8080 does not work for
some people so we got another IP address for our VM and put Mailmain on
port 80 there. However, this means we also have to have a different DNS (A)
record to point to that different IP which means a different host name. So
sqlite.org:8080 was changed to mailinglists.sqlite.org for this.

So I updated mailman today to use mailinglists.sqlite.org rather than
sqlite.org:8080 knowing that there is a good chance some issues will arise.
I have been fixing them as they surface. This issue is related to the
Postfix config not recognizing mailinglists.sqlite.org. I've updated it an
restarted postfix so this should in theory fix it.

Just let me know if there are more issues and I'll address them in turn.
Sorry for the inconvenience.



On Fri, Feb 13, 2015 at 6:37 PM, R.Smith  wrote:

> I can confirm the bounces happen for the ".mailinglists" email address
> which is now automatically added to the "Reply-To" address.
>
> I hit the reply-to-all button and then remove the .mailinglists address to
> fix it, but it is rather cumbersome, if the powers that control such things
> could kindly adjust that setting it will be most appreciated.
>
>
>
> On 2/14/2015 2:04 AM, Simon Slavin wrote:
>
>> On 13 Feb 2015, at 11:39pm, David King  wrote:
>>
>>  Maybe unrelated, but in the last few hours the list ID header changed
>>> from "sqlite-users.sqlite.org" to "sqlite-users.mailinglists.sqlite.org",
>>> which messes up my mail filtering.
>>>
>> Thanks, David.  That was it.
>>
>> For others: messages from the list now reach me with a 'From' header
>> which includes 'mailinglists.'.  So when I hit 'reply' that's the address
>> my message goes to.  Whereas when I start a new thread my mailer uses the
>> address in my contact list which is the proper address.
>>
>> Thanks to David for helping me figure that out so quickly.  I hand-edited
>> the 'To' header on this message and I expect it'll go through.
>>
>> Simon.
>>
>>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
Mike

[sqlite] test for bounce detection

[David King]

Also FYI:

I sent this last one to both sqlite-users at mailinglists.sqlite.org and 
sqlite-users at sqlite.org, and the one to sqlite-users at 
mailinglists.sqlite.org bounced with the same "Relay Access Denied" but the 
other one went through.



On 13 Feb 2015, at 15:39, David King  wrote:

> Maybe unrelated, but in the last few hours the list ID header changed from 
> "sqlite-users.sqlite.org" to "sqlite-users.mailinglists.sqlite.org", which 
> messes up my mail filtering.
> 
> Of course I'll fix it locally, I only mention in because it might be related 
> to whatever server config changes have been taking place.
> 
> 
> 
> On 13 Feb 2015, at 15:27, Simon Slavin  wrote:
> 
>> This is a test message.  I just sent another message to the list and it got 
>> bounced with the message "Relay access denied" so I want to see if this one 
>> made it.
>> 
>> If it does, can the listadmin see if there's anything wrong ?  Sorry to 
>> occupy your Friday night or weekend.
>> 
>> Simon.
>> ___
>> sqlite-users mailing list
>> sqlite-users at mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>> 
> 
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: 

[sqlite] test for bounce detection

[David King]

Maybe unrelated, but in the last few hours the list ID header changed from 
"sqlite-users.sqlite.org" to "sqlite-users.mailinglists.sqlite.org", which 
messes up my mail filtering.

Of course I'll fix it locally, I only mention in because it might be related to 
whatever server config changes have been taking place.



On 13 Feb 2015, at 15:27, Simon Slavin  wrote:

> This is a test message.  I just sent another message to the list and it got 
> bounced with the message "Relay access denied" so I want to see if this one 
> made it.
> 
> If it does, can the listadmin see if there's anything wrong ?  Sorry to 
> occupy your Friday night or weekend.
> 
> Simon.
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> 

-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: 

Re: [sqlite] How to get access to SQLite Test Harness #3(TH3)

[Richard Hipp]

On Thu, Jun 26, 2014 at 1:55 AM, Kishore Reddy  wrote:

>
> *Richard Hipp,*
> I am planning to use SQLite library in *Avionics Level B software*.
>

SQLite is developed using a DO-178B compatible process.  The 100% MC/DC
testing is just one aspect of that.  Contact our office for details.

-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] How to get access to SQLite Test Harness #3(TH3)

[Kishore Reddy]

Hi  *Roger Binns*,
Thanks for the reply.Actually i wasnt checking mail-list for answer i
thought i will be getting mail to my gmail that is the reason i posted on
developers forum too.

*Richard Hipp*,
i dont see any reply from you in the mail-list.


*Roger Binns/*

*Richard Hipp,*
I am planning to use SQLite library in *Avionics Level B software*.For that
i need to prove that this software complies to *DO-178B standards*.For that
i need to prove that it follows some 64 objectives set by DO-178B .

Ex)Listed below are some of the 64 objectives

*Planning Documents:*
1)Plan for software aspects of certification
2)Software development plan
3)software verification plan
4)software configuration management plan
5)software quality assurance plan
6)software requirements standards
7)software design standards
8)software coding standards

*Verification Documents:*

1)Software verification cases & Procedures
2)software verification results
3)software configuration management records
4)software configuration index
5)bug reports
6)software quality assurance records
7)software conformity review
8)software accomplishment summary

So i want to know where to get all these documents or information for
*SQLite*





On Tue, Jun 24, 2014 at 11:39 AM, Kishore Reddy  wrote:

> Hi,
> a)I want to use sqlite library in my project software.In the website it is
> listed as TH3 achieves 100% branch test coverage.I want all the test
> results of the SQLite software which shows that the software has *100%
> statement+branch coverage*.Can any one tell me how to get these test
> results ?? or how to get this TH3 framework and run those test cases to get
> results?
> b)Do we have requirements for this SQLite software which provides
> *traceability* to the test cases provided by TH3 framework?
>
>
>
>
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] How to get access to SQLite Test Harness #3(TH3)

[Roger Binns]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 23/06/14 23:09, Kishore Reddy wrote:
> a)I want to use sqlite library in my project software.In the website it
> is listed as TH3 achieves 100% branch test coverage.

The SQLite software as released has already been tested with TH3 and
passed.  You do not need the TH3 test suite just to use SQLite.  Really:

 https://sqlite.org/testing.html

> b)Do we have requirements for this SQLite software which provides 
> *traceability* to the test cases provided by TH3 framework?

You can purchase a license for TH3.  See the last section of
https://sqlite.org/th3.html

Roger

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlOpHNMACgkQmOOfHg372QQEZACeIlRc/4JICpbQNbajdWfTlffr
0WUAoMRjzQcDTpz9PHGWk5oxrpRauwX/
=paUV
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] How to get access to SQLite Test Harness #3(TH3)

[Kishore Reddy]

Hi,
a)I want to use sqlite library in my project software.In the website it is
listed as TH3 achieves 100% branch test coverage.I want all the test
results of the SQLite software which shows that the software has *100%
statement+branch coverage*.Can any one tell me how to get these test
results ?? or how to get this TH3 framework and run those test cases to get
results?
b)Do we have requirements for this SQLite software which provides
*traceability* to the test cases provided by TH3 framework?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test for pending writes ?

[Richard Hipp]

On Wed, Apr 2, 2014 at 5:59 PM, Adrian Soundy <
adrian.sou...@integration.co.nz> wrote:

>
>
> Is there a Sqlite method that will tell me if there is any pending writes
> from another process so I can end and commit the current transaction
> straight away ?
>

No.  Doing that would require some kind of interprocess communication (IPC)
and we are not aware of any standard, cross-platform, reliable IPC
mechanism that is up to the task.  Sorry.

-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Test for pending writes ?

[Adrian Soundy]

Hello,

 

I have a process on an embedded device that is continuously updating the
database in WAL mode. To get the performance we require in the busy cases we
put everything in to transactions.  

 

Sometimes another process  needs to write to the same database in a timely
manner.

 

Is there a Sqlite method that will tell me if there is any pending writes
from another process so I can end and commit the current transaction
straight away ?

 

Cheers

Adrian Soundy

 

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test

[e-mail mgbg25171]

please ignore
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test ignore

[e-mail mgbg25171]

test
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test failures on Ubuntu

[brijesh_philips]

Hi,

Really appretiate if some one can point out how can i debug the failures


Thanks



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Test-failures-on-Ubuntu-tp65874p65933.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Test failures on Ubuntu

[brijesh_philips]

Hi,

I am getting failures in the below tests while doing the regression test on
Ubuntu 
with ,
SHA1 Hash: ba8d08b67021a32fda069c18b7eb93523e6f0d1f 
Date: 2012-11-27 21:56:28

Most of the failures are, 

Expected: [1 1]
 Got: [0 {}]

Are these errors serious, How to fix these ?

Thank You
Brijesh

142 errors out of 2083931 tests
Failures on these tests: 
altermalloc-1.transient.19 
attachmalloc-1.transient.19 
attachmalloc-1.transient.63 
attachmalloc-1.transient.361 
attachmalloc-1.transient.580 
attachmalloc-2.transient.237 
malloc-1.transient.19 
malloc-10.transient.19 
malloc-13.transient.21 
malloc-14.transient.19 
malloc-17.transient.21 
malloc-20.transient.19 
malloc-20.transient.57 
malloc-26.transient.19 
malloc6-1.transient.19 
mallocD-4.transient.21 
mallocG-1.transient.19 
shared_err-5.transient.21 
shared_malloc-8.64.cleanup.1 
shared_malloc-8.65.cleanup.1 
shared_malloc-8.66.cleanup.1 
shared_malloc-8.67.cleanup.1 
shared_malloc-8.68.cleanup.1 
shared_malloc-8.64.cleanup.1 
shared_malloc-8.65.cleanup.1 
shared_malloc-8.66.cleanup.1 
shared_malloc-8.67.cleanup.1 
shared_malloc-8.68.cleanup.1 
no_optimization.where-14.1 
no_optimization.where-14.2 
no_optimization.where-14.3 
no_optimization.where-14.4 
no_optimization.where-14.7.2 
memsubsys1.altermalloc-1.transient.18 
memsubsys1.attachmalloc-1.transient.18 
memsubsys1.attachmalloc-1.transient.61 
memsubsys1.attachmalloc-1.transient.354 
memsubsys1.attachmalloc-1.transient.569 
memsubsys1.attachmalloc-2.transient.233 
memsubsys1.malloc-1.transient.18 
memsubsys1.malloc-10.transient.18 
memsubsys1.malloc-13.transient.20 
memsubsys1.malloc-14.transient.18 
memsubsys1.malloc-17.transient.20 
memsubsys1.malloc-20.transient.18 
memsubsys1.malloc-20.transient.55 
memsubsys1.malloc-26.transient.18 
memsubsys1.malloc6-1.transient.18 
memsubsys1.mallocD-4.transient.20 
memsubsys1.mallocG-1.transient.18 
memsubsys2.altermalloc-1.transient.19 
memsubsys2.attachmalloc-1.transient.19
memsubsys2.attachmalloc-1.transient.63 
memsubsys2.attachmalloc-1.transient.361 
memsubsys2.attachmalloc-1.transient.580 
memsubsys2.attachmalloc-2.transient.237 
memsubsys2.malloc-1.transient.19 
memsubsys2.malloc-10.transient.19 
memsubsys2.malloc-13.transient.21 
memsubsys2.malloc-14.transient.19 
memsubsys2.malloc-17.transient.21 
memsubsys2.malloc-20.transient.19 
memsubsys2.malloc-20.transient.57 
memsubsys2.malloc-26.transient.19 
memsubsys2.malloc6-1.transient.19 
memsubsys2.mallocD-4.transient.21 
memsubsys2.mallocG-1.transient.19 
exclusive.malloc-1.transient.19 
exclusive.malloc-10.transient.22 
exclusive.malloc-13.transient.15 
exclusive.malloc-14.transient.19 
exclusive.malloc-17.transient.21 
exclusive.malloc-20.transient.19 
exclusive.malloc-20.transient.62 
exclusive.malloc-26.transient.22 
persistent_journal_error.malloc-1.transient.19 
persistent_journal_error.malloc-10.transient.19
 persistent_journal_error.malloc-13.transient.15 
 persistent_journal_error.malloc-14.transient.19 
 persistent_journal_error.malloc-17.transient.21 
 persistent_journal_error.malloc-20.transient.19 
 persistent_journal_error.malloc-20.transient.113 
 persistent_journal_error.malloc-26.transient.19 
 no_journal_error.malloc-1.transient.19 
 no_journal_error.malloc-10.transient.19 
 no_journal_error.malloc-13.transient.15 
 no_journal_error.malloc-14.transient.19 
 no_journal_error.malloc-17.transient.21 
 no_journal_error.malloc-20.transient.19 
 no_journal_error.malloc-20.transient.113 
 no_journal_error.malloc-26.transient.19 
 no_mutex_try.altermalloc-1.transient.19 
 no_mutex_try.attachmalloc-1.transient.19 
 no_mutex_try.attachmalloc-1.transient.63 
 no_mutex_try.attachmalloc-1.transient.361 
 no_mutex_try.attachmalloc-1.transient.580 
 no_mutex_try.attachmalloc-2.transient.237 
 no_mutex_try.malloc-1.transient.19 
 no_mutex_try.malloc-10.transient.19 
 no_mutex_try.malloc-13.transient.21 
 no_mutex_try.malloc-14.transient.19 
 no_mutex_try.malloc-17.transient.21 
 no_mutex_try.malloc-20.transient.19 
 no_mutex_try.malloc-20.transient.57 
 no_mutex_try.malloc-26.transient.19 
 no_mutex_try.malloc6-1.transient.19 
 no_mutex_try.mallocD-4.transient.21 
 no_mutex_try.mallocG-1.transient.19 
 journaltest.altermalloc-1.transient.22 
 journaltest.attachmalloc-1.transient.22 
 journaltest.attachmalloc-1.transient.69 
 journaltest.attachmalloc-1.transient.407 
 journaltest.attachmalloc-1.transient.661 
 journaltest.attachmalloc-2.transient.272 
 journaltest.malloc-1.transient.19 
 journaltest.malloc-10.transient.19 
 journaltest.malloc-13.transient.21 
 journaltest.malloc-14.transient.19 
 journaltest.malloc-17.transient.21 
 journaltest.malloc-20.transient.19 
 journaltest.malloc-20.transient.57 
 journaltest.malloc-26.transient.19 
 journaltest.malloc6-1.transient.19 
 journaltest.mallocD-4.transient.21 
 journaltest.mallocG-1.transient.19 
 inmemory_journal.altermalloc-1.transient.19 
 inmemory_journal.attachmalloc-1.transient.19 
 

Re: [sqlite] Running SQLite Test Suites

[Grace Batumbya]

> The "test" target is in the file "main.mk" which is "include"-ed by the very 
> last line of Makefile.linux-gcc.

Thanks Richard. That clears up things.

--
Grace Batumbya 
Research Assistant | Seneca CDOT 
Phone: 416-491-5050 x3548 
cdot.senecac.on.ca 

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Running SQLite Test Suites

[Richard Hipp]

The "test" target is in the file "main.mk" which is "include"-ed by the
very last line of Makefile.linux-gcc.

On Mon, Jun 11, 2012 at 1:33 PM, Grace Batumbya <
grace.batum...@senecacollege.ca> wrote:

> >./configure; make test
>
> >
>
> >I just ran it on Solaris, as shown above, and it appears to be working
> fine.  You will need a relatively recent version of TCL, however.  8.5 or
> 8.6.
>
>
>
> From the REAME file:
>
> ... If the configure script does not work out for you, there is a generic
> makefile named "Makefile.linux-gcc" in the top directory of the source tree
> that you can copy and edit to suit your needs
>
>
>
> The reason "make test" was not working for us is because
> Makefile.linux-gcc does not contain the test targets.
>
>
>
> Is there a reason why the test targets are not included in the generic
> makefile?
>
>
>
> Thanks.
>
> --
>
> Grace Batumbya
>
> Research Assistant | Seneca CDOT
>
> Phone: 416-491-5050 x3548
>
> cdot.senecac.on.ca
>
>
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Running SQLite Test Suites

[Grace Batumbya]

>./configure; make test

>

>I just ran it on Solaris, as shown above, and it appears to be working fine.  
>You will need a relatively recent version of TCL, however.  8.5 or 8.6.



>From the REAME file:

... If the configure script does not work out for you, there is a generic 
makefile named "Makefile.linux-gcc" in the top directory of the source tree 
that you can copy and edit to suit your needs



The reason "make test" was not working for us is because Makefile.linux-gcc 
does not contain the test targets.



Is there a reason why the test targets are not included in the generic makefile?



Thanks.

--

Grace Batumbya

Research Assistant | Seneca CDOT

Phone: 416-491-5050 x3548

cdot.senecac.on.ca


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Running SQLite Test Suites

[Richard Hipp]

On Thu, Jun 7, 2012 at 11:51 AM, Carl Desautels <
carlin.desaut...@senecacollege.ca> wrote:

> Hi,
>
> A partner and I have downloaded the SQLite core source and made some
> alterations, and we can successfully build the source.
> However we would like to know how to run the TCL test suite, resources
> online suggest simply running $make test/alltest.I feel like this resource
> is out of date because that make option does not exist, could someone point
> me in the right direction to get TCL tests running?
>


./configure; make test

I just ran it on Solaris, as shown above, and it appears to be working
fine.  You will need a relatively recent version of TCL, however.  8.5 or
8.6.


> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Running SQLite Test Suites

[Carl Desautels]

Hi,

A partner and I have downloaded the SQLite core source and made some
alterations, and we can successfully build the source.
However we would like to know how to run the TCL test suite, resources
online suggest simply running $make test/alltest.I feel like this resource
is out of date because that make option does not exist, could someone point
me in the right direction to get TCL tests running?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Test message, please ignore...

[sqlite]

Test.

--
Joe Mistachkin

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test Foreign Key Column

[M.Ozeau]

Thx a lot Jonathan,

Pragma seems to be just the thing i was looking for !

Regards, MoZo

2011/4/26 Jonathan Allin <jonat...@jonathanallin.com>

> I had to use the pragmas:
> # foreign_key_list
> # foreign_keys
>
> But also the sqlite_master table includes the command used to create each
> table. Foreign fields will have a REFERENCES key word.
>
> Regards,
>
> ¬Jonathan
>
> -Original Message-
> From: sqlite-users-boun...@sqlite.org
> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of M.Ozeau
> Sent: 26 April 2011 17:06
> To: sqlite-users@sqlite.org
> Subject: [sqlite] Test Foreign Key Column
>
> Hi and sorry for my poor English.
>
> I want to know if is it possible to test if a column is a foreign key. I
> mean, where the "constraint" is stored ?
> The only system table i know for Sqlite is the "sqlite_master" but can't
> find anything in her for the foreign key.
>
> For example, if i have a table "Person", and a Table "Country" , i can have
> a integer column 'Country_ID' as foreign key in my table "Person".
>
> Is there any method to test, (i mean in sql language) if the integer column
> 'Country_ID' is used as a foreign key or if it's just an integer column
>
> --
> Cordialy  MoZo
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
Cordialement Morgan Ozeau
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test Foreign Key Column

[Jonathan Allin]

I had to use the pragmas:
# foreign_key_list
# foreign_keys

But also the sqlite_master table includes the command used to create each
table. Foreign fields will have a REFERENCES key word.

Regards,

¬Jonathan

-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of M.Ozeau
Sent: 26 April 2011 17:06
To: sqlite-users@sqlite.org
Subject: [sqlite] Test Foreign Key Column

Hi and sorry for my poor English.

I want to know if is it possible to test if a column is a foreign key. I
mean, where the "constraint" is stored ?
The only system table i know for Sqlite is the "sqlite_master" but can't
find anything in her for the foreign key.

For example, if i have a table "Person", and a Table "Country" , i can have
a integer column 'Country_ID' as foreign key in my table "Person".

Is there any method to test, (i mean in sql language) if the integer column
'Country_ID' is used as a foreign key or if it's just an integer column

--
Cordialy  MoZo
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Test Foreign Key Column

[M.Ozeau]

Hi and sorry for my poor English.

I want to know if is it possible to test if a column is a foreign key. I
mean, where the "constraint" is stored ?
The only system table i know for Sqlite is the "sqlite_master" but can't
find anything in her for the foreign key.

For example, if i have a table "Person", and a Table "Country" , i can have
a integer column 'Country_ID' as foreign key in my table "Person".

Is there any method to test, (i mean in sql language) if the integer column
'Country_ID' is used as a foreign key or if it's just an integer column

-- 
Cordialy  MoZo
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] test/exists.test 2.$tn.1 fails if both DBs are in WAL mode

[Dan Kennedy]

 >> For me, this test from test/exists.test fails if both database
 >> connections are opened in WAL mode, that is if "PRAGMA journal_mode=WAL"
 >> is issued right after each DB is opened.
 >>
 >># TABLE objects.
 >>#
 >>do_test   {
 >>  sql1 { DROP TABLE IF EXISTS t1 }
 >>  sql2 { CREATE TABLE t1(x) }
 >>  sql1 { DROP TABLE IF EXISTS t1 }
 >>  sql2 { SELECT name FROM sqlite_master WHERE type = 'table' }
 >>} {}

On 04/10/2011 04:12 PM, Ralf Junker wrote:
> The test passes well if I recreate the database file anew just prior to
> running it so it acts upon an empty database.

The [do_multiclient_test] is supposed to delete the database file
before running the script passed as the third argument (of which
this [do_test] is a part). So you're right, it is supposed to run
starting with an empty database.

Dan.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test/exists.test 2.$tn.1 fails if both DBs are in WAL mode

[Ralf Junker]

For me, this test from test/exists.test fails if both database
connections are opened in WAL mode, that is if "PRAGMA journal_mode=WAL"
is issued right after each DB is opened.

  # TABLE objects.
  #
  do_test{
sql1 { DROP TABLE IF EXISTS t1 }
sql2 { CREATE TABLE t1(x) }
sql1 { DROP TABLE IF EXISTS t1 }
sql2 { SELECT name FROM sqlite_master WHERE type = 'table' }
  } {}

This is against http://www.sqlite.org/src/info/f346dae127.

I am running a ported version of the test instead of the original tcl so
my finding could wrong. Still, I believe it better to let you know in
case you want to check this last-minute change before you release 3.7.6.

Ralf
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] test/exists.test 2.$tn.1 fails if both DBs are in WAL mode

[Ralf Junker]

The test passes well if I recreate the database file anew just prior to
running it so it acts upon an empty database.

If this is what is intended, I apologize for the false alarm.

Ralf

On 10.04.2011 10:28, Ralf Junker wrote:

> For me, this test from test/exists.test fails if both database
> connections are opened in WAL mode, that is if "PRAGMA journal_mode=WAL"
> is issued right after each DB is opened.
> 
>   # TABLE objects.
>   #
>   do_test  {
> sql1 { DROP TABLE IF EXISTS t1 }
> sql2 { CREATE TABLE t1(x) }
> sql1 { DROP TABLE IF EXISTS t1 }
> sql2 { SELECT name FROM sqlite_master WHERE type = 'table' }
>   } {}
> 
> This is against http://www.sqlite.org/src/info/f346dae127.
> 
> I am running a ported version of the test instead of the original tcl so
> my finding could wrong. Still, I believe it better to let you know in
> case you want to check this last-minute change before you release 3.7.6.
> 
> Ralf
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test/exists.test 2.$tn.1 fails if both DBs are in WAL mode

[Ralf Junker]

For me, this test from test/exists.test fails if both database
connections are opened in WAL mode, that is if "PRAGMA journal_mode=WAL"
is issued right after each DB is opened.

  # TABLE objects.
  #
  do_test{
sql1 { DROP TABLE IF EXISTS t1 }
sql2 { CREATE TABLE t1(x) }
sql1 { DROP TABLE IF EXISTS t1 }
sql2 { SELECT name FROM sqlite_master WHERE type = 'table' }
  } {}

This is against http://www.sqlite.org/src/info/f346dae127.

I am running a ported version of the test instead of the original tcl so
my finding could wrong. Still, I believe it better to let you know in
case you want to check this last-minute change before you release 3.7.6.

Ralf
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test DBD::SQLite 1.30_04 - write-ahead logging

[Darren Duncan]

All,

I am pleased to announce that DBD::SQLite (Self Contained RDBMS in a Perl DBI
Driver) version 1.30_04 has been released on CPAN (by Adam Kennedy).

   http://search.cpan.org/~adamk/DBD-SQLite-1.30_04/

This developer release bundles the brand-new SQLite version 3.7.2, which (since 
3.7.0) adds support for write-ahead logging (WAL).  See 
http://sqlite.org/wal.html for the details of the WAL support that SQLite now 
has.

WAL is an alternative method to how SQLite implements atomic commit and 
rollback 
than to its rollback journal method.  It offers much improved concurrency and 
performance in many circumstances, such as because database readers and writers 
don't block each other.  There are also trade-offs.  By default, SQLite and 
DBD::SQLite will continue to use the older rollback journal method, and you can 
use the new WAL method with the SQL command:

   PRAGMA journal_mode=WAL;

There are also numerous other additions, changes, or fixes in either 
DBD::SQLite 
or SQLite itself since the last production DBD::SQLite release 1.29 of 2010 
January, which bundles SQLite 3.6.22.  For the change details since then, see 
http://sqlite.org/changes.html or 
http://search.cpan.org/src/ADAMK/DBD-SQLite-1.30_04/Changes as appropriate.

TESTING NEEDED!

Please bash the hell out of the latest DBD::SQLite and report any outstanding
bugs on RT.  Test your dependent or compatible projects with it, which includes
any DBMS-wrapping or object persistence modules, and applications.

This 1.30_04 release will probably be released as a production 1.31 within a 
week if no show-stopper problems are found.

Please note the compatibility caveats of using pre-3.7.x versions of SQLite on 
databases that had been used with WAL mode on.  In order to use an older SQLite 
on the database, the database must have last been used by a 3.7.x in journal 
mode.  See http://sqlite.org/wal.html for details.

Please note that, if you receive nondescript "disk I/O error" errors from your 
code after the update, see if the failing code involves a process fork followed 
by unlinking of the database, such as if it was temporary for testing.  The 
DBD::SQLite test suite had needed an update to act more correctly, which the 
update to 3.7.x from 3.6.x exposed; 3.6.x didn't complain about this.

If you want in to DBD::SQLite development, then join the following email/IRC
forums which MST created (the mailing list, I am administrating):

   http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite

   #dbd-sqlite on irc.perl.org

And the canonical version control is at:

   http://svn.ali.as/cpan/trunk/DBD-SQLite/

Patches welcome.  Ideas welcome.  Testing welcome.

If you feel that a bug you find is in SQLite itself rather than the Perl DBI
driver for it, the main users email forum for SQLite in general is at:

   http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

... where you can report it as an appropriate list post (the SQLite issue
tracking system is no longer updateable by the public; posting in the list can
cause an update there by a registered SQLite developer).

Please do not reply to me directly with your responses.  Instead send them to
the forums or file with RT as is appropriate.

Thank you. -- Darren Duncan

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] how to get the sqlite test case?

[A.]

The official test-suite is proprietary. If you really wish to get your
hands on it, you may enter in a contract with Hwaci as seen described at
http://sqlite.org/consortium.html

On Tue, 2010-02-23 at 08:55 +0800, xuecaili wrote:
> Hello!
> I'm a sqlite user and I want to use sqlite to develop a 
> software.  But at first, I'd like to test sqlite. It is declared in the 
> official web site that how sqlite is tested. I want to get the test case 
> you test the sqlite, especially 7.2 million queries run with the SQL 
> TEST LOGIC which is a test harness described in the web site. Can you 
> provide these 7.2 million queries?  I'll appreciate it!  Thank you very 
 I. much!


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] how to get the sqlite test case?

[Jay A. Kreibich]

On Tue, Feb 23, 2010 at 08:55:31AM +0800, xuecaili scratched on the wall:
> Hello!
> I'm a sqlite user and I want to use sqlite to develop a 
> software.  But at first, I'd like to test sqlite. It is declared in the 
> official web site that how sqlite is tested. I want to get the test case 
> you test the sqlite, especially 7.2 million queries run with the SQL 
> TEST LOGIC which is a test harness described in the web site. Can you 
> provide these 7.2 million queries?  I'll appreciate it!  Thank you very 
> much!

  If you're looking at this page:

  http://www.sqlite.org/sqllogictest/doc/tip/about.wiki

  Click "files" at the top.  This is a Fossil repository for the
  sqllogictest package.  See: http://www.fossil-scm.org/

-j

-- 
Jay A. Kreibich < J A Y  @  K R E I B I.C H >

"Our opponent is an alien starship packed with atomic bombs.  We have
 a protractor."   "I'll go home and see if I can scrounge up a ruler
 and a piece of string."  --from Anathem by Neal Stephenson
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] how to get the sqlite test case?

[xuecaili]

Hello!
I'm a sqlite user and I want to use sqlite to develop a 
software.  But at first, I'd like to test sqlite. It is declared in the 
official web site that how sqlite is tested. I want to get the test case 
you test the sqlite, especially 7.2 million queries run with the SQL 
TEST LOGIC which is a test harness described in the web site. Can you 
provide these 7.2 million queries?  I'll appreciate it!  Thank you very 
much!
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test harness?

[Tim Romano]

I am encountering significant differences in the way the data libraries 
for SQLite produced by a "major player" are handling joins, unions, and 
inline views, in combination, compared to several other GUI front ends 
for SQLite which have been well-received and which jibe with each 
other.  Is there a standard test-harness that will reveal the degree of 
SQLite-compatibility of these libraries?  Can I point these libraries at 
a harness database, run a set of standard queries, and compare the 
results with what ought to have been produced?



___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test DBD::SQLite 1.26_06 please

[Darren Duncan]

All,

I am pleased to announce that DBD::SQLite (Self Contained RDBMS in a Perl DBI
Driver) version 1.26_06 has been released on CPAN (by Adam Kennedy).

   http://search.cpan.org/~adamk/DBD-SQLite-1.26_06/

TESTING NEEDED!

Please bash the hell out of the latest DBD::SQLite and report any outstanding
bugs on RT.  Test your dependent or compatible projects with it, which includes
any DBMS-wrapping or object persistence modules, and applications.

This developer release includes both several changes which *might break your 
applications* if not accounted for, and it has a lot of code refactoring.

This release should also fix the known problem with full-text search (FTS3) 
that 
was reported in the 1.26_05 release but had existed in many prior versions; the 
included test for that problem now passes.

 From the Changes file:

 *** CHANGES THAT MAY POSSIBLY BREAK YOUR OLD APPLICATIONS ***
 - Removed undocumented (and most probably unused) reset method
   from a statement handle (which was only accessible via func().)
   Simply use "$sth->finish" instead. (ISHIGAKI)
 - Now DBD::SQLite supports foreign key constraints by default.
   Long-ignored foreign keys (typically written for other DB
   engines) will start working. If you don't want this feature,
   issue a pragma to disable foreign keys. (ISHIGAKI)
 - Renamed "unicode" attribute to "sqlite_unicode" for integrity.
   Old "unicode" attribute is still accessible but will be
   deprecated in the near future. (ISHIGAKI)

 - You can see file/line info while tracing even if you compile
   with a non-gcc compiler. (ISHIGAKI)
 - Major code refactoring. (ISHIGAKI)
 - Pod reorganized, and some of the missing bits (including
   pragma) are added. (ISHIGAKI)

The bundled SQLite version (3.6.19) is unchanged from last time.

If you want in to DBD::SQLite development, then join the following email/IRC
forums which MST created (the mailing list, I am administrating):

   http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite

   #dbd-sqlite on irc.perl.org

And the canonical version control is at:

   http://svn.ali.as/cpan/trunk/DBD-SQLite/

Patches welcome.  Ideas welcome.  Testing welcome.  Whining is also welcome!

If you feel that a bug you find is in SQLite itself rather than the Perl DBI
driver for it, the main users email forum for SQLite in general is at:

   http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

... where you can report it as an appropriate list post (the SQLite issue
tracking system is no longer updateable by the public; posting in the list can
cause an update there by a registered SQLite developer).

Please do not reply to me directly with your responses.  Instead send them to
the forums or file with RT as is appropriate.

Thank you. -- Darren Duncan

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] test DBD::SQLite 1.26_05 - foreign keys!

[P Kishor]

On Thu, Oct 15, 2009 at 11:49 PM, P Kishor  wrote:
> On Thu, Oct 15, 2009 at 11:37 PM, Darren Duncan  
> wrote:
>> P Kishor wrote [on sqlite-us...@sqlite.org]:
>>>
>>> On Thu, Oct 15, 2009 at 1:39 AM, Darren Duncan 
>>> wrote:

 All,

 I am pleased to announce that DBD::SQLite (Self Contained RDBMS in a Perl
 DBI
 Driver) version 1.26_05 has been released on CPAN (by Adam Kennedy).

>>> ..

 P.S.  DBD::SQLite has at least 1 known bug, also in version 1.25, with
 regard to
 full-text search (FTS3); there is an included new failing test, which
 currently
 is set to skip so the CPAN testers don't issue fails,
>>>
>>> I tried to create a db with FTS3 and got the following
>>>
>>> perl(12546) malloc: *** error for object 0x1eb160: Non-aligned pointer
>>> being freed (2)
>>> *** set a breakpoint in malloc_error_break to debug
>>> perl(12546) malloc: *** error for object 0x870200: double free
>>> *** set a breakpoint in malloc_error_break to debug
>>> perl(12546) malloc: *** error for object 0x1ea668: Non-aligned pointer
>>> being freed
>>> *** set a breakpoint in malloc_error_break to debug
>>> Segmentation fault
>>>
>>> Is the above the FTS3 related error?
>>
>> Looks similar.  This is the official bug report that we already have, which
>> was reported on Oct 14, and on which the failing/skipping test is based:
>>
>>  http://rt.cpan.org/Public/Bug/Display.html?id=50503
>>
>>  Subject: Segfault with fts3
>>
>> A copy of the ticket text is displayed below the dashed line in this email
>> also.
>>
>> The bug report was against DBD::SQLite versions that bundled SQLite 3.6.13
>> and 3.6.18 respectively, for both of which the bug manifests.
>>
>> As of yet the bug is unfixed.
>>
>> If you have any new information, it would be useful for you to add it to the
>> above RT ticket.
>>
>
>
> Well, the only additional information I have is that I went back to
> DBD::SQLite 1.21, and that compiled fine and also was able to create
> and populate FTS3 tables. However, and this is weird, it keeps on
> periodically choking up on MATCH queries. I have a web app on my
> laptop, and when I query the db using FTS3, I get back an "Internal
> Server Error" ("Premature end of script headers" in the Apache error
> log), but if I reload the page a few times, I will suddenly get the
> search result back. Reload, and the process repeats. Error a couple,
> three times, and then, get the correct results.
>
> This is all very mysterious, and very disheartening.
>
>
>

Ok. Perhaps a bit more on the mystery I was experiencing with
DBD::SQLite 1.21. I was getting periodic 500 errors, and nothing
illuminating in the Apache logs as well. I finally figured out from
the command line... I am still getting occasional segmentation fault
with DBD::SQLite 1.21. Will roll back even more and see what I get.



-- 
Puneet Kishor http://www.punkish.org
Carbon Model http://carbonmodel.org
Charter Member, Open Source Geospatial Foundation http://www.osgeo.org
Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor
Nelson Institute, UW-Madison http://www.nelson.wisc.edu
---
Assertions are politics; backing up assertions with evidence is science
===
Sent from Madison, WI, United States
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] test DBD::SQLite 1.26_05 - foreign keys!

[P Kishor]

On Thu, Oct 15, 2009 at 11:37 PM, Darren Duncan  wrote:
> P Kishor wrote [on sqlite-us...@sqlite.org]:
>>
>> On Thu, Oct 15, 2009 at 1:39 AM, Darren Duncan 
>> wrote:
>>>
>>> All,
>>>
>>> I am pleased to announce that DBD::SQLite (Self Contained RDBMS in a Perl
>>> DBI
>>> Driver) version 1.26_05 has been released on CPAN (by Adam Kennedy).
>>>
>> ..
>>>
>>> P.S.  DBD::SQLite has at least 1 known bug, also in version 1.25, with
>>> regard to
>>> full-text search (FTS3); there is an included new failing test, which
>>> currently
>>> is set to skip so the CPAN testers don't issue fails,
>>
>> I tried to create a db with FTS3 and got the following
>>
>> perl(12546) malloc: *** error for object 0x1eb160: Non-aligned pointer
>> being freed (2)
>> *** set a breakpoint in malloc_error_break to debug
>> perl(12546) malloc: *** error for object 0x870200: double free
>> *** set a breakpoint in malloc_error_break to debug
>> perl(12546) malloc: *** error for object 0x1ea668: Non-aligned pointer
>> being freed
>> *** set a breakpoint in malloc_error_break to debug
>> Segmentation fault
>>
>> Is the above the FTS3 related error?
>
> Looks similar.  This is the official bug report that we already have, which
> was reported on Oct 14, and on which the failing/skipping test is based:
>
>  http://rt.cpan.org/Public/Bug/Display.html?id=50503
>
>  Subject: Segfault with fts3
>
> A copy of the ticket text is displayed below the dashed line in this email
> also.
>
> The bug report was against DBD::SQLite versions that bundled SQLite 3.6.13
> and 3.6.18 respectively, for both of which the bug manifests.
>
> As of yet the bug is unfixed.
>
> If you have any new information, it would be useful for you to add it to the
> above RT ticket.
>


Well, the only additional information I have is that I went back to
DBD::SQLite 1.21, and that compiled fine and also was able to create
and populate FTS3 tables. However, and this is weird, it keeps on
periodically choking up on MATCH queries. I have a web app on my
laptop, and when I query the db using FTS3, I get back an "Internal
Server Error" ("Premature end of script headers" in the Apache error
log), but if I reload the page a few times, I will suddenly get the
search result back. Reload, and the process repeats. Error a couple,
three times, and then, get the correct results.

This is all very mysterious, and very disheartening.



-- 
Puneet Kishor http://www.punkish.org
Carbon Model http://carbonmodel.org
Charter Member, Open Source Geospatial Foundation http://www.osgeo.org
Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor
Nelson Institute, UW-Madison http://www.nelson.wisc.edu
---
Assertions are politics; backing up assertions with evidence is science
===
Sent from Madison, WI, United States
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] test DBD::SQLite 1.26_05 - foreign keys!

[Darren Duncan]

P Kishor wrote [on sqlite-us...@sqlite.org]:
> On Thu, Oct 15, 2009 at 1:39 AM, Darren Duncan  
> wrote:
>> All,
>>
>> I am pleased to announce that DBD::SQLite (Self Contained RDBMS in a Perl DBI
>> Driver) version 1.26_05 has been released on CPAN (by Adam Kennedy).
>>
> ..
>> P.S.  DBD::SQLite has at least 1 known bug, also in version 1.25, with 
>> regard to
>> full-text search (FTS3); there is an included new failing test, which 
>> currently
>> is set to skip so the CPAN testers don't issue fails,
> 
> I tried to create a db with FTS3 and got the following
> 
> perl(12546) malloc: *** error for object 0x1eb160: Non-aligned pointer
> being freed (2)
> *** set a breakpoint in malloc_error_break to debug
> perl(12546) malloc: *** error for object 0x870200: double free
> *** set a breakpoint in malloc_error_break to debug
> perl(12546) malloc: *** error for object 0x1ea668: Non-aligned pointer
> being freed
> *** set a breakpoint in malloc_error_break to debug
> Segmentation fault
> 
> Is the above the FTS3 related error?

Looks similar.  This is the official bug report that we already have, which was 
reported on Oct 14, and on which the failing/skipping test is based:

   http://rt.cpan.org/Public/Bug/Display.html?id=50503

   Subject: Segfault with fts3

A copy of the ticket text is displayed below the dashed line in this email also.

The bug report was against DBD::SQLite versions that bundled SQLite 3.6.13 and 
3.6.18 respectively, for both of which the bug manifests.

As of yet the bug is unfixed.

If you have any new information, it would be useful for you to add it to the 
above RT ticket.

-- Darren Duncan



[text/plain 790b]
The attached script fails on 1.25 and 1.26_04. It does one of three things:

- segfaults
- gives a double free error
- hangs without any cpu activity

Which of the above three it does depends on the exact script (adding or
removing a print line can change its behavior), but it always fails.

Here are a couple sample error messages:
*** glibc detected *** double free or corruption (!prev):
0x0083c480 ***
Abort (core dumped)

Segmentation fault (core dumped)

The database doesn't appear to be corrupted after the failure -- running
an integrity check with the sqlite3 command line binary says the db is okay.

The equivalent code without the fts3 module works fine.

I did a quick test with the DBD::SQLite packaged with the latest Ubuntu
(1.14), and that version seems to work.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] test DBD::SQLite 1.26_05 - foreign keys!

[P Kishor]

On Thu, Oct 15, 2009 at 1:39 AM, Darren Duncan  wrote:
> All,
>
> I am pleased to announce that DBD::SQLite (Self Contained RDBMS in a Perl DBI
> Driver) version 1.26_05 has been released on CPAN (by Adam Kennedy).
>
..
>
> P.S.  DBD::SQLite has at least 1 known bug, also in version 1.25, with regard 
> to
> full-text search (FTS3); there is an included new failing test, which 
> currently
> is set to skip so the CPAN testers don't issue fails,

I tried to create a db with FTS3 and got the following

perl(12546) malloc: *** error for object 0x1eb160: Non-aligned pointer
being freed (2)
*** set a breakpoint in malloc_error_break to debug
perl(12546) malloc: *** error for object 0x870200: double free
*** set a breakpoint in malloc_error_break to debug
perl(12546) malloc: *** error for object 0x1ea668: Non-aligned pointer
being freed
*** set a breakpoint in malloc_error_break to debug
Segmentation fault


Is the above the FTS3 related error?


-- 
Puneet Kishor http://www.punkish.org
Carbon Model http://carbonmodel.org
Charter Member, Open Source Geospatial Foundation http://www.osgeo.org
Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor
Nelson Institute, UW-Madison http://www.nelson.wisc.edu
---
Assertions are politics; backing up assertions with evidence is science
===
Sent from Madison, WI, United States
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [DBD-SQLite] test DBD::SQLite 1.26_05 - foreign keys!

[Adam Kennedy]

Please note the following correction to the announcement.

Whining is also welcome. :)

Adam K

2009/10/15 Darren Duncan :
> Patches welcome.  Ideas welcome.  Testing welcome.  Whining to /dev/null.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test DBD::SQLite 1.26_05 - foreign keys!

[Darren Duncan]

All,

I am pleased to announce that DBD::SQLite (Self Contained RDBMS in a Perl DBI 
Driver) version 1.26_05 has been released on CPAN (by Adam Kennedy).

   http://search.cpan.org/~adamk/DBD-SQLite-1.26_05/

This developer release bundles the brand-new SQLite version 3.6.19, which adds 
support for enforcing SQL foreign keys.  See http://sqlite.org/foreignkeys.html 
for the details of the foreign key support that SQLite now has.

Also be sure to look at the section 
http://sqlite.org/foreignkeys.html#fk_enable 
, because you have to enable a pragma on each connect to use the foreign keys 
feature; it isn't yet on by default for backwards compatibility purposes.

As I imagine many of you have been pining away for SQLite to support this 
feature for a long while, you'll want to dig in right away.

TESTING NEEDED!

Please bash the hell out of the latest DBD::SQLite and report any outstanding
bugs on RT.  Test your dependent or compatible projects with it, which includes
any DBMS-wrapping or object persistence modules, and applications.

And especially try actually using foreign keys with SQLite.

As the official release announcement says:  "This release has been extensively 
tested (we still have 100% branch test coverage).  [The SQLite developers] 
consider this release to be production ready.  Nevertheless, testing can only 
prove the presence of bugs, not their absence.  So if you encounter problems, 
please let us know."

See also http://www.sqlite.org/changes.html for a list of everything else that 
changed in SQLite itself over the last few months.

If you want in to DBD::SQLite development, then join the following email/IRC
forums which MST created (the mailing list, I am administrating):

   http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite

   #dbd-sqlite on irc.perl.org

And the canonical version control is at:

   http://svn.ali.as/cpan/trunk/DBD-SQLite/

Patches welcome.  Ideas welcome.  Testing welcome.  Whining to /dev/null.

If you feel that a bug you find is in SQLite itself rather than the Perl DBI 
driver for it, the main users email forum for SQLite in general is at:

   http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

... where you can report it as an appropriate list post (the SQLite issue 
tracking system is no longer updateable by the public; posting in the list can 
cause an update there by a registered SQLite developer).

Please do not reply to me directly with your responses.  Instead send them to
the forums or file with RT as is appropriate.

Thank you. -- Darren Duncan

P.S.  DBD::SQLite has at least 1 known bug, also in version 1.25, with regard 
to 
full-text search (FTS3); there is an included new failing test, which currently 
is set to skip so the CPAN testers don't issue fails, but the issue behind it 
should hopefully be fixed before the next DBD::SQLite release.  We decided that 
shipping DBD::SQLite now with the skipping test was preferable to waiting for 
that fix so you could get the new foreign keys feature the soonest.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Platforms on which SQLite test cases are run

[D. Richard Hipp]

On May 8, 2009, at 2:47 PM, mwnn wrote:

> Hi,
>  The page at http://www.sqlite.org/testing.html quotes
> "Prior to each check-in to the SQLite source tree, developers  
> typically run
> a subset (called "veryquick") of the Tcl tests consisting of about  
> 41.7
> thousand test cases and covering 97.07% of the core SQLite source  
> code."
> Are the test cases run only on x86 architecture running Linux?

Tests are run on x86 and x86_64 linux, MacOS 10.5 x86, win32, and  
win64.  No MIPS.

D. Richard Hipp
d...@hwaci.com



___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Platforms on which SQLite test cases are run

[mwnn]

Hi,
  The page at http://www.sqlite.org/testing.html quotes
"Prior to each check-in to the SQLite source tree, developers typically run
a subset (called "veryquick") of the Tcl tests consisting of about 41.7
thousand test cases and covering 97.07% of the core SQLite source code."
Are the test cases run only on x86 architecture running Linux?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] test error

[Martin.Engelschalk]

hi,

attachments do not reach this list, please specify the error.

Martin

AVINASH MITTAL schrieb:
>   
> Hi,
>
> while executing tests for amalgamation for version 3.6.5 i got this error, 
> can somebody help me in this regard
>
> Regards
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
>   

-- 

* Codeswift GmbH *
Traunstr. 30
A-5026 Salzburg-Aigen
Tel: +49 (0) 8662 / 494330
Mob: +49 (0) 171 / 4487687
Fax: +49 (0) 12120 / 204645
[EMAIL PROTECTED]
www.codeswift.com / www.swiftcash.at

Codeswift Professional IT Services GmbH
Firmenbuch-Nr. FN 202820s
UID-Nr. ATU 50576309

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test error

[AVINASH MITTAL]

  
Hi,

while executing tests for amalgamation for version 3.6.5 i got this error, can 
somebody help me in this regard

Regards
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite test suite - where is it?

[Dan]

On Sep 8, 2008, at 11:05 PM, Ribeiro, Glauber wrote:

> Sorry for the newbie question, but how is the regression testing
> invoked?
>
> I tried "make check" with the 3.6.2 "amalgamation" distribution in  
> Unix,
> but that seemed to do nothing.

You only get the test suite if you download the full source tree. This
one:

   http://www.sqlite.org/sqlite-3.6.2.tar.gz

Do "make test". You'll need tcl installed to run the test suite.

Dan.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] SQLite test suite - where is it?

[Ribeiro, Glauber]

Sorry for the newbie question, but how is the regression testing
invoked?

I tried "make check" with the 3.6.2 "amalgamation" distribution in Unix,
but that seemed to do nothing.

Thanks,

glauber
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test suite failures on 3.6.2 on x86_64

[Frederik Himpe]

When building sqlite 3.6.2 on Mandriva Linux Cooker x86_64, some tests 
fail:

12 errors out of 23377 tests
Failures on these tests: lookaside-1.4 lookaside-1.5 memsubsys1-2.3 
memsubsys1-2.4 memsubsys1-3.2.4 memsubsys1-4.3 memsubsys1-4.4 
memsubsys1-5.3 memsubsys1-6.3 memsubsys1-6.4 memsubsys1-7.4 memsubsys1-7.5

on Mandriva Cooker i586 there is no problem at all, and with sqlite 3.6.1 
on x86_64 the testsuite succeeds too, so this seems like a regression.

Any idea what could be wrong?

Complete x86_64 build log: http://artipc10.vub.ac.be/files/log.sqlite3.gz

-- 
Frederik Himpe

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite Test Scripts

[Dennis Cote]

Alex Katebi wrote:
> How can I run the SQLite TCL test scripts?
> 

You need a unix like build environment and TCL installed. Then simply 
use configure and make

../sqlite/configure
make test

This will build the test fixture program and run the test suite. To run 
tests manually you need to start the testfixture and pass it one of the 
test scripts.

./testfixture ../sqlite/test/xyz.test

Where xyz is the name of the test script you want to run.

HTH
Dennis Cote
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] SQLite Test Scripts

[Alex Katebi]

How can I run the SQLite TCL test scripts?

Thanks,
-Alex
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Test insert4-2.4.1 in insert4.test

[Noah Hart]

I don't have TCL, so I'm trying to validate sqlite by running some of
the tests by hand.

In insert4.test, there is a sub-test 

do_test insert4-2.4.1 {
  execsql {
DELETE FROM t3;
INSERT INTO t3 SELECT DISTINCT * FROM t2;
SELECT * FROM t3;
  }
} {9 1 1 9}


I can run this test by hand, using the following commands 
SQLite version 3.5.7
Enter ".help" for instructions
sqlite> CREATE TABLE t2(x int, y int);
sqlite> CREATE TABLE t3(a int, b int);
sqlite> INSERT INTO t2 VALUES(9,1);
sqlite> INSERT INTO t2 SELECT y, x FROM t2;
sqlite> SELECT * FROM t2;
9|1
1|9
sqlite>
sqlite> INSERT INTO t3 SELECT DISTINCT * FROM t2;
sqlite> SELECT * FROM t3;
1|9
9|1

Notice the difference in the ordering of the rows.

When I run the same INSERT without the DISTINCT keyword, I get the
expected results

sqlite> DELETE FROM T3;
sqlite> INSERT INTO t3 SELECT * FROM t2;
sqlite> SELECT * FROM t3;
9|1
1|9


So, I have 2 questions:
1) Does this test work when running from tcl?
2) If so, what is different?

Regards,

Noah



CONFIDENTIALITY NOTICE: 
This message may contain confidential and/or privileged information. If you are 
not the addressee or authorized to receive this for the addressee, you must not 
use, copy, disclose, or take any action based on this message or any 
information herein. If you have received this message in error, please advise 
the sender immediately by reply e-mail and delete this message. Thank you for 
your cooperation.


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] test post via gmane

[Adam Megacz]

Hopefully now that sqlite-users is on mailman it will take posts sent
via gmane.  If this message shows up, then that is the case.

  - a


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Test suite

[Joe Wilson]

Grab the source tree via tar.gz file or cvs and run:

  ./configure
  make test
or
  make fulltest

To run just a single test file:

  make testfixture# if not already built by make test

  ./testfixture test/select1.test

--- Ken <[EMAIL PROTECTED]> wrote:
> Sorry if this has been asked, but I'd like to know how to run the test suite.




  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] Test suite

[Ken]

Sorry if this has been asked, but I'd like to know how to run the test suite.

I could not find any documentation on this on the sqlite website.

Thanks for your help.
Ken

Re: [sqlite] test failures on cygwin

[jim-on-linux]

On Saturday 22 September 2007 14:20, Evans, Mark (Tandem) wrote:
> It's hard to drag my Linux server to Starbucks.  :-)
>
> Next Windows laptop, though, will definitely have to have a
> Linux/Windows dual personality.  I'll have to wait until the next
> mega-merger for a Mac.
>
> Mark
>

If your  HD has the space load Suse Linux from Novel and run Windos or 
Linux.  You can down load for free Novel's latest version.

jim-on-linux
http://www.inqvista.com





> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Friday, September 21, 2007 6:05 PM
> > To: sqlite-users@sqlite.org
> > Subject: Re: [sqlite] test failures on cygwin
>
> 
>
> > Of course, the easiest option by far is to use a Linux box or
> > a Mac. :-)
> >
> > --
> > D. Richard Hipp <[EMAIL PROTECTED]>
>
> ---
>-- To unsubscribe, send email to
> [EMAIL PROTECTED]
> ---
>--

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] test failures on cygwin

[Evans, Mark (Tandem)]

It's hard to drag my Linux server to Starbucks.  :-)  

Next Windows laptop, though, will definitely have to have a
Linux/Windows dual personality.  I'll have to wait until the next
mega-merger for a Mac.

Mark

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Friday, September 21, 2007 6:05 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] test failures on cygwin
> 

>
> Of course, the easiest option by far is to use a Linux box or 
> a Mac. :-)
> 
> --
> D. Richard Hipp <[EMAIL PROTECTED]>
> 

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] test failures on cygwin

[Gerry Snyder]

Evans, Mark (Tandem) wrote:




So it looks like I have a cygwin TCL issue.  Is this fixable?
You can load Active State Tcl and use that instead of the version that 
comes with Cygwin.


You get lots of extra goodies, in addition to an up-to-date Tcl core.

HTH,

Gerry

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] test failures on cygwin

[drh]

"Evans, Mark (Tandem)" <[EMAIL PROTECTED]> wrote:
> **
> N.B.:  The version of TCL that you used to build this test harness
> is defective in that it does not support 64-bit integers.  Some or
> all of the test failures above might be a result from this defect
> in your TCL build.
> **

Yeah.  That's what I figured.  You need to fix you TCL build.

It's *still* not to late to switch to Linux or Mac  :-)

--
D. Richard Hipp <[EMAIL PROTECTED]>


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] test failures on cygwin

[drh]

"Evans, Mark (Tandem)" <[EMAIL PROTECTED]> wrote:
> Hi all,
> 
> I have been lurking on the message board and am in awe of the collective
> wisdom.
> 
> I'm just getting my feet wet learning the internals of SQLite, drinking
> from the proverbial firehose.  I am using cygwin 1.90 as my learning
> platform and I have built SQLite 3.5.0.   I ran 'make test' (quick.test
> suite) and it reports some test failures as follows:
> 
> 41 errors out of 28604 tests
> Failures on these tests: autoinc-6.1 bind-3.1 cast-3.1 cast-3.2 cast-3.4
> cast-3.5 cast-3.6 cast-3.8 cast-3.11 cast-3.12 cast-3.14 cast-3.15
> cast-3.16 cast-3.18 cast-3.21 cast-3.22 cast-3.24 expr-1.102 expr-1.106
> func-18.14 func-18.16 func-18.17 func-18.31 lastinsert-8.1
> lastinsert-9.1 misc1-9.1 misc2-4.1 misc2-4.2 misc2-4.4 misc2-4.5
> misc2-4.6 misc3-3.6 misc3-3.7 misc3-3.8 misc3-3.9 misc3-3.10 misc3-3.11
> misc5-2.2 shared-1.11.9 shared-2.11.9 types-2.1.8
> 
> Should I be surprised by these failures?  
> 
> Taking the first one that failed, autoinc-6.1, it reported:
> 
> autoinc-6.1...
> Expected: [9223372036854775807]
>  Got: [-1]
> 
> The corresonding test code is:
> 
> ifcapable {!rowid32} {
>   do_test autoinc-6.1 {
> execsql {
>   CREATE TABLE t6(v INTEGER PRIMARY KEY AUTOINCREMENT, w);
>   INSERT INTO t6 VALUES(9223372036854775807,1);
>   SELECT seq FROM main.sqlite_sequence WHERE name='t6';
> }
>   } 9223372036854775807
> }
> 
> So the SELECT clause returns -1 instead of the expected
> 0x7FFF (MAXLONGLONG), or in other words MAXLONGLONG + 1.
> Should the value returned by SELECT seq ... be the the key value (rowid)
> of the last insert, or, is seq supposed to represent the next rowid
> (autoincrement of last key)?
> 

41 failures out of 28604 isn't bad.  That's a 0.1% failure rate.  If
these are the only problems you are having, your build is probably OK.

If you want to go for 100% pass, the first place I would look is what
version of TCL you are linking against to build the test harness.
You want a later version of 8.4 or any version of 8.5.  I'll bet you
have 8.3, which won't work here.

The other thing you might try to do is *not* use cygwin but instead
use mingw.

Of course, the easiest option by far is to use a Linux box or a Mac. :-)

--
D. Richard Hipp <[EMAIL PROTECTED]>



-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] test failures on cygwin

[Evans, Mark (Tandem)]

When I  run just autoinc.test alone,  I get the following summary
output:

54 errors out of 66 tests
Failures on these tests: autoinc-6.1 autoinc-1.1 autoinc-1.2 autoinc-1.3
autoinc-1.4 autoinc-1.6 autoinc-2.1 autoinc-2.2 autoinc-2.3 autoinc-2.4
autoinc-2.5 autoinc-2.6 autoinc-2.7 autoinc-2.8 autoinc-2.9 autoinc-2.10
autoinc-2.11 autoinc-2.12 autoinc-2.13 autoinc-2.21 autoinc-2.23
autoinc-2.25 autoinc-2.27 autoinc-2.29 autoinc-2.51 autoinc-2.52
autoinc-2.53 autoinc-2.54 autoinc-2.55 autoinc-2.70 autoinc-2.71
autoinc-2.72 autoinc-2.73 autoinc-2.74 autoinc-3.1 autoinc-3.2
autoinc-3.3 autoinc-3.4 autoinc-4.1 autoinc-4.2 autoinc-4.3 autoinc-4.4
autoinc-4.4.1 autoinc-4.5 autoinc-4.6 autoinc-4.7 autoinc-4.8
autoinc-4.9 autoinc-4.10 autoinc-5.1 autoinc-5.2 autoinc-5.3 autoinc-5.4
autoinc-7.1
**
N.B.:  The version of TCL that you used to build this test harness
is defective in that it does not support 64-bit integers.  Some or
all of the test failures above might be a result from this defect
in your TCL build.
**
All memory allocations freed - no leaks
Maximum memory usage: 76060 bytes


So it looks like I have a cygwin TCL issue.  Is this fixable?
 
Mark

> -Original Message-
> From: Evans, Mark (Tandem) 
> Sent: Friday, September 21, 2007 5:47 PM
> To: sqlite-users@sqlite.org
> Subject: [sqlite] test failures on cygwin
> 
> Hi all,
> 
> I have been lurking on the message board and am in awe of the 
> collective wisdom.
> 
> I'm just getting my feet wet learning the internals of 
> SQLite, drinking from the proverbial firehose.  I am using 
> cygwin 1.90 as my learning
> platform and I have built SQLite 3.5.0.   I ran 'make test' 
> (quick.test
> suite) and it reports some test failures as follows:
> 
> 41 errors out of 28604 tests
> Failures on these tests: autoinc-6.1 bind-3.1 cast-3.1 
> cast-3.2 cast-3.4
> cast-3.5 cast-3.6 cast-3.8 cast-3.11 cast-3.12 cast-3.14 cast-3.15
> cast-3.16 cast-3.18 cast-3.21 cast-3.22 cast-3.24 expr-1.102 
> expr-1.106
> func-18.14 func-18.16 func-18.17 func-18.31 lastinsert-8.1
> lastinsert-9.1 misc1-9.1 misc2-4.1 misc2-4.2 misc2-4.4 misc2-4.5
> misc2-4.6 misc3-3.6 misc3-3.7 misc3-3.8 misc3-3.9 misc3-3.10 
> misc3-3.11
> misc5-2.2 shared-1.11.9 shared-2.11.9 types-2.1.8
> 
> Should I be surprised by these failures?  
> 
> Taking the first one that failed, autoinc-6.1, it reported:
> 
> autoinc-6.1...
> Expected: [9223372036854775807]
>  Got: [-1]
> 
> The corresonding test code is:
> 
> ifcapable {!rowid32} {
>   do_test autoinc-6.1 {
> execsql {
>   CREATE TABLE t6(v INTEGER PRIMARY KEY AUTOINCREMENT, w);
>   INSERT INTO t6 VALUES(9223372036854775807,1);
>   SELECT seq FROM main.sqlite_sequence WHERE name='t6';
> }
>   } 9223372036854775807
> }
> 
> So the SELECT clause returns -1 instead of the expected 
> 0x7FFF (MAXLONGLONG), or in other words MAXLONGLONG + 1.
> Should the value returned by SELECT seq ... be the the key 
> value (rowid) of the last insert, or, is seq supposed to 
> represent the next rowid (autoincrement of last key)?
> 
> Regards,
> Mark
> 
> 
> --
> ---
> To unsubscribe, send email to [EMAIL PROTECTED]
> --
> ---
> 
> 

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] test failures on cygwin

[Evans, Mark (Tandem)]

Hi all,

I have been lurking on the message board and am in awe of the collective
wisdom.

I'm just getting my feet wet learning the internals of SQLite, drinking
from the proverbial firehose.  I am using cygwin 1.90 as my learning
platform and I have built SQLite 3.5.0.   I ran 'make test' (quick.test
suite) and it reports some test failures as follows:

41 errors out of 28604 tests
Failures on these tests: autoinc-6.1 bind-3.1 cast-3.1 cast-3.2 cast-3.4
cast-3.5 cast-3.6 cast-3.8 cast-3.11 cast-3.12 cast-3.14 cast-3.15
cast-3.16 cast-3.18 cast-3.21 cast-3.22 cast-3.24 expr-1.102 expr-1.106
func-18.14 func-18.16 func-18.17 func-18.31 lastinsert-8.1
lastinsert-9.1 misc1-9.1 misc2-4.1 misc2-4.2 misc2-4.4 misc2-4.5
misc2-4.6 misc3-3.6 misc3-3.7 misc3-3.8 misc3-3.9 misc3-3.10 misc3-3.11
misc5-2.2 shared-1.11.9 shared-2.11.9 types-2.1.8

Should I be surprised by these failures?  

Taking the first one that failed, autoinc-6.1, it reported:

autoinc-6.1...
Expected: [9223372036854775807]
 Got: [-1]

The corresonding test code is:

ifcapable {!rowid32} {
  do_test autoinc-6.1 {
execsql {
  CREATE TABLE t6(v INTEGER PRIMARY KEY AUTOINCREMENT, w);
  INSERT INTO t6 VALUES(9223372036854775807,1);
  SELECT seq FROM main.sqlite_sequence WHERE name='t6';
}
  } 9223372036854775807
}

So the SELECT clause returns -1 instead of the expected
0x7FFF (MAXLONGLONG), or in other words MAXLONGLONG + 1.
Should the value returned by SELECT seq ... be the the key value (rowid)
of the last insert, or, is seq supposed to represent the next rowid
(autoincrement of last key)?

Regards,
Mark


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] test fixture tcl errors on Windows

[Joe Wilson]

a better patch...

Index: test/exclusive2.test
===
RCS file: /sqlite/sqlite/test/exclusive2.test,v
retrieving revision 1.4
diff -u -3 -p -r1.4 exclusive2.test
--- test/exclusive2.test16 Apr 2007 15:02:20 -  1.4
+++ test/exclusive2.test25 Apr 2007 03:05:04 -
@@ -161,6 +161,7 @@ do_test exclusive2-2.4 {
   seek $fd 1024
   puts -nonewline $fd [string repeat [binary format c 0] 1]
   flush $fd
+  close $fd
   t1sig
 } $::sig
 
@@ -242,4 +243,8 @@ do_test exclusive2-3.6 {
   pagerChangeCounter test.db
 } {5}
 
+db close
+file delete -force test.db
+file delete -force test.db-journal
+
 finish_test



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] test fixture tcl errors on Windows

[Joe Wilson]

The test script itself has the test.db open, and as result Windows cannot
delete an open file. It worked on UNIX because you can delete anything at 
any time whether it is open, running, locked or whatever.

If you apply this patch, exclusive2.test will run to completion on cygwin
without error. It ought to work on MinGW as well.


Index: test/exclusive2.test
===
RCS file: /sqlite/sqlite/test/exclusive2.test,v
retrieving revision 1.4
diff -u -3 -p -r1.4 exclusive2.test
--- test/exclusive2.test16 Apr 2007 15:02:20 -  1.4
+++ test/exclusive2.test25 Apr 2007 02:42:56 -
@@ -161,6 +161,7 @@ do_test exclusive2-2.4 {
   seek $fd 1024
   puts -nonewline $fd [string repeat [binary format c 0] 1]
   flush $fd
+  close $fd
   t1sig
 } $::sig
 

--- Dennis Cote <[EMAIL PROTECTED]> wrote:

> I'm getting a strange failure of the test suite on Windows (XP all 
> updates). The exclusive2 test is getting a permission denied error when 
> deleting a file. I can manually delete the file and the tclsh can 
> execute the same file delete command if I enter it manually.
> 
> $ ./testfixture.exe ../sqlite/test/exclusive2.test
> exclusive2-1.0... Ok
> exclusive2-1.1... Ok
> exclusive2-1.2... Ok
> exclusive2-1.3... Ok
> exclusive2-1.4... Ok
> exclusive2-1.5... Ok
> exclusive2-1.6... Ok
> exclusive2-1.7... Ok
> exclusive2-1.9... Ok
> exclusive2-1.10... Ok
> exclusive2-1.11... Ok
> exclusive2-2.1... Ok
> exclusive2-2.2... Ok
> exclusive2-2.3... Ok
> exclusive2-2.4... Ok
> exclusive2-2.5... Ok
> exclusive2-2.6... Ok
> exclusive2-2.7... Ok
> exclusive2-2.8... Ok
> c:\SQLite\SQLiteV3\build\testfixture.exe: error deleting "test.db": 
> permission denied
> while executing
> "file delete -force test.db"
> (file "../sqlite/test/exclusive2.test" line 192)
> 
> $ ls test.db
> test.db
> 
> $ tclsh
> file delete -force test.db
> exit
> 
> $ ls test.db
> ls: test.db: No such file or directory
> 
> I'm building SQLite and running these tests using MinGW/MSYS. I haven't 
> had any problems before, but I haven't built sqlite from source since 
> around version 3.3.12.


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] test fixture tcl errors on Windows

[Dennis Jenkins]

Dennis Cote wrote:


I don't know enough TCL to know if there is a subtle bug here or not. 
I suspect that perhaps the file isn't really being closed until the 
script exits.Does this seem possible?


Dennis Cote


Get "filemon" from www.sysinternals.com.  Set a filter to monitor all 
files in the directory containing the database file (or some other 
reasonable filter expression).  Comment out all of the tests from the 
script that pass.  Then fire it up :)



-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] test fixture tcl errors on Windows

[Dennis Cote]

[EMAIL PROTECTED] wrote:


My guess is that your virus scanning software is opening
the test.db file as sson as SQLite closes it, in order to
check it for new viruses.  The test script tries to delete
the file right after closing it, but it can't because the
virus scanner has it open.

  
I don't have a virus scanner on this PC. It sits behind a virus scanning 
firewall, and they trust us enough not to put in virus laden disks. I 
don't have any indexing software either. I did have an explorer window 
open displaying that directory, but I get the same result with that 
window closed.


I just skipped the exclusive2 tests by editing the exclude list in the 
quick test file. All other test run to completion. I got one error due 
to differences in floating point exponent formating between TCL on 
windows and linux (at least that is my suspicion).


   alter-7.1...
   Expected: [text 1 integer -2 text 5.4e-8 real 5.4e-08]
Got: [text 1 integer -2 text 5.4e-8 real 5.4e-008]

I just can't see why it can't delete that file.

I modified the exclusive2.test file and wrapped the file delete commands 
in catch blocks so they wouldn't halt the test, and then changed the 
name of the database file used for the 3.x tests from test.db to 
test3.db. I also added a pair of file delete commands in catch blocks to 
remove the test3.db file. Now when I run this test set I get no failures.


   $ ./testfixture.exe ../sqlite/test/exclusive2.test
   exclusive2-1.0... Ok
   exclusive2-1.1... Ok
   exclusive2-1.2... Ok
   exclusive2-1.3... Ok
   exclusive2-1.4... Ok
   exclusive2-1.5... Ok
   exclusive2-1.6... Ok
   exclusive2-1.7... Ok
   exclusive2-1.9... Ok
   exclusive2-1.10... Ok
   exclusive2-1.11... Ok
   exclusive2-2.1... Ok
   exclusive2-2.2... Ok
   exclusive2-2.3... Ok
   exclusive2-2.4... Ok
   exclusive2-2.5... Ok
   exclusive2-2.6... Ok
   exclusive2-2.7... Ok
   exclusive2-2.8... Ok
   exclusive2-3.0... Ok
   exclusive2-3.1... Ok
   exclusive2-3.2... Ok
   exclusive2-3.3... Ok
   exclusive2-3.4... Ok
   exclusive2-3.5... Ok
   exclusive2-3.6... Ok
   Thread-specific data deallocated properly
   0 errors out of 27 tests
   Failures on these tests:

But I can see that neither the test.db file or the new test3.db were 
deleted.


The only thing I can see that is common to these files is that they are 
both passed to the pagerChangeCounter command which is only used in this 
test.


   proc pagerChangeCounter {filename {new ""}} {
 set fd [open $filename RDWR]
 fconfigure $fd -translation binary -encoding binary
 if {$new ne ""} {
   seek $fd 24
   set a [expr {($new&0xFF00)>>24}]
   set b [expr {($new&0x00FF)>>16}]
   set c [expr {($new&0xFF00)>>8}]
   set d [expr {($new&0x00FF)}]
   puts -nonewline $fd [binary format  $a $b $c $d]
   flush $fd
 }

 seek $fd 24
 foreach {a b c d} [list 0 0 0 0] {}
 binary scan [read $fd 4]  a b c d
 set  ret [expr ($a&0x00FF)<<24]
 incr ret [expr ($b&0x00FF)<<16]
 incr ret [expr ($c&0x00FF)<<8]
 incr ret [expr ($d&0x00FF)<<0]

 close $fd
 return $ret
   }

I don't know enough TCL to know if there is a subtle bug here or not. I 
suspect that perhaps the file isn't really being closed until the script 
exits.Does this seem possible?


Dennis Cote

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] test fixture tcl errors on Windows

[drh]

Dennis Cote <[EMAIL PROTECTED]> wrote:
> I'm getting a strange failure of the test suite on Windows (XP all 
> updates).
> exclusive2-2.8... Ok
> c:\SQLite\SQLiteV3\build\testfixture.exe: error deleting "test.db": 
> permission denied
> while executing
> "file delete -force test.db"
> (file "../sqlite/test/exclusive2.test" line 192)
> 
> 
> Do any of you TCL experts have any idea what could be wrong?
> 

My guess is that your virus scanning software is opening
the test.db file as sson as SQLite closes it, in order to
check it for new viruses.  The test script tries to delete
the file right after closing it, but it can't because the
virus scanner has it open.

--
D. Richard Hipp <[EMAIL PROTECTED]>


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] test fixture tcl errors on Windows

[Dennis Cote]

I'm getting a strange failure of the test suite on Windows (XP all 
updates). The exclusive2 test is getting a permission denied error when 
deleting a file. I can manually delete the file and the tclsh can 
execute the same file delete command if I enter it manually.


   $ ./testfixture.exe ../sqlite/test/exclusive2.test
   exclusive2-1.0... Ok
   exclusive2-1.1... Ok
   exclusive2-1.2... Ok
   exclusive2-1.3... Ok
   exclusive2-1.4... Ok
   exclusive2-1.5... Ok
   exclusive2-1.6... Ok
   exclusive2-1.7... Ok
   exclusive2-1.9... Ok
   exclusive2-1.10... Ok
   exclusive2-1.11... Ok
   exclusive2-2.1... Ok
   exclusive2-2.2... Ok
   exclusive2-2.3... Ok
   exclusive2-2.4... Ok
   exclusive2-2.5... Ok
   exclusive2-2.6... Ok
   exclusive2-2.7... Ok
   exclusive2-2.8... Ok
   c:\SQLite\SQLiteV3\build\testfixture.exe: error deleting "test.db": 
permission denied

   while executing
   "file delete -force test.db"
       (file "../sqlite/test/exclusive2.test" line 192)

   $ ls test.db
   test.db

   $ tclsh
   file delete -force test.db
   exit

   $ ls test.db
   ls: test.db: No such file or directory

I'm building SQLite and running these tests using MinGW/MSYS. I haven't 
had any problems before, but I haven't built sqlite from source since 
around version 3.3.12.


Do any of you TCL experts have any idea what could be wrong?

TIA
Dennis Cote


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] test message ...

[Rob Sciuk]

Please ignore this test -- sorry.

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] test mail - plz ignore

[jayanth KP]

Re: [sqlite] test program won't run anymore! sqliteBtreeOpen: Assertion 'seizeof...

[Peter Cunderlik]

I'd try the following:

1. make completely sure you're linking against the correct SQLite
library. Are you linking dynamically or statically?

2. turn all optimizations off (CFLAGS="" before running ./configure),
compile, link and test your app.

3. grab the pre-configured SQLite sources
(http://www.sqlite.org/download.html , the .zip files), compile, link
and test your app.

4. if everything fails, repeat steps 1-3 in random order until it gets
working! :-)

5. if desperate enough, use gdb to track down the problem or modify
the SQLite sources to print out debug info (e.g. sizeof(ptr)). Why
should the size of this pointer be different than sizeof(char *)? Try
to simulate this check in your own test program.

Peter

On 7/24/06, Keiichi McGuire <[EMAIL PROTECTED]> wrote:

I'm pretty sure my gcc is not broken (although I'm not sure how to check
specifically for this problem).
I can compile stuff with gcc without a problem as long as the sqlite stuff
is not on there.

-Keiichi

Re: [sqlite] test program won't run anymore! sqliteBtreeOpen: Assertion 'seizeof...

[Keiichi McGuire]

I'm pretty sure my gcc is not broken (although I'm not sure how to check
specifically for this problem).
I can compile stuff with gcc without a problem as long as the sqlite stuff
is not on there.

-Keiichi

On 7/24/06, Jay Sprenkle <[EMAIL PROTECTED]> wrote:


On 7/24/06, Keiichi McGuire <[EMAIL PROTECTED]> wrote:
> Previously when I went into sqlite via command line I could not create a
> table, and I would get that same error message.
> So what I did was that I reinstalled sqlite, to a different directory so
I
> can keep my other version to see if I can find any differences.  The
good
> thing is that the reinstalled sqlite works, however when I use gcc to
> compile the code, and then trying to execute, I still get the same error
> message.  Am I missing something here?

sounds like your gcc is broken or incompatible?

Re: [sqlite] test program won't run anymore! sqliteBtreeOpen: Assertion 'seizeof...

[Jay Sprenkle]

On 7/24/06, Keiichi McGuire <[EMAIL PROTECTED]> wrote:

Previously when I went into sqlite via command line I could not create a
table, and I would get that same error message.
So what I did was that I reinstalled sqlite, to a different directory so I
can keep my other version to see if I can find any differences.  The good
thing is that the reinstalled sqlite works, however when I use gcc to
compile the code, and then trying to execute, I still get the same error
message.  Am I missing something here?


sounds like your gcc is broken or incompatible?

Re: [sqlite] test program won't run anymore! sqliteBtreeOpen: Assertion 'seizeof...

[Keiichi McGuire]

Previously when I went into sqlite via command line I could not create a
table, and I would get that same error message.
So what I did was that I reinstalled sqlite, to a different directory so I
can keep my other version to see if I can find any differences.  The good
thing is that the reinstalled sqlite works, however when I use gcc to
compile the code, and then trying to execute, I still get the same error
message.  Am I missing something here?
Thanks!


On 7/24/06, Keiichi McGuire <[EMAIL PROTECTED]> wrote:


nope, i was actually using the right sqlite, since the other one actually
gave me an architecture error.

any ideas?


On 7/24/06, Keiichi McGuire < [EMAIL PROTECTED]> wrote:
>
> nope, compiler is still the same (gcc).
>
> actually... i think i might have the answer. Might have jumped the gun
> on the question.  I did install a version of sqlite that is for arm-linux,
> and that would be why it's not compiling.  let me double check and I will
> post again :), sorry if it was a false alarm!!
> -Keiichi
>
>
> On 7/24/06, Jay Sprenkle < [EMAIL PROTECTED]> wrote:
> >
> > On 7/24/06, Keiichi McGuire <[EMAIL PROTECTED]> wrote:
> > > test: ../sqlite-2.8.17/src/btree.c:702: sqliteBtreeOpen: Assertion
> > > 'sizeof(ptr)==sizeof(char*)' failed.
> > > Aborted
> >
> >
> > Did you change compilers?
> > Or compile the DLL on a different version than you compiled the test
> > program?
> >
>
>

Re: [sqlite] test program won't run anymore! sqliteBtreeOpen: Assertion 'seizeof...

[Keiichi McGuire]

nope, i was actually using the right sqlite, since the other one actually
gave me an architecture error.

any ideas?

On 7/24/06, Keiichi McGuire <[EMAIL PROTECTED]> wrote:


nope, compiler is still the same (gcc).

actually... i think i might have the answer. Might have jumped the gun on
the question.  I did install a version of sqlite that is for arm-linux, and
that would be why it's not compiling.  let me double check and I will post
again :), sorry if it was a false alarm!!
-Keiichi


On 7/24/06, Jay Sprenkle <[EMAIL PROTECTED]> wrote:
>
> On 7/24/06, Keiichi McGuire <[EMAIL PROTECTED]> wrote:
> > test: ../sqlite-2.8.17/src/btree.c:702: sqliteBtreeOpen: Assertion
> > 'sizeof(ptr)==sizeof(char*)' failed.
> > Aborted
>
>
> Did you change compilers?
> Or compile the DLL on a different version than you compiled the test
> program?
>

Re: [sqlite] test program won't run anymore! sqliteBtreeOpen: Assertion 'seizeof...

[Keiichi McGuire]

nope, compiler is still the same (gcc).

actually... i think i might have the answer. Might have jumped the gun on
the question.  I did install a version of sqlite that is for arm-linux, and
that would be why it's not compiling.  let me double check and I will post
again :), sorry if it was a false alarm!!
-Keiichi

On 7/24/06, Jay Sprenkle <[EMAIL PROTECTED]> wrote:


On 7/24/06, Keiichi McGuire <[EMAIL PROTECTED]> wrote:
> test: ../sqlite-2.8.17/src/btree.c:702: sqliteBtreeOpen: Assertion
> 'sizeof(ptr)==sizeof(char*)' failed.
> Aborted


Did you change compilers?
Or compile the DLL on a different version than you compiled the test
program?