Re: [sqlite] When to close a db, take 2...

On Mon, Jun 21, 2010 at 11:56:09PM -0400, Sam Carleton scratched on the wall: > I am NEVER capturing anything in the log file, so it looks like everything > is returning the correct. I am a bit stumped right now, so if it is alright, > I am going to post my code: If you're doing a double

[sqlite] When to close a db, take 2...

Ok, after a bit of testing this evening, the close which is crashing the system has ALWAYS been the same close statement, the close after the Apache Module has initialized the data structure to process the request. I went in and made sure that each and every sqlite call is log if there is a

Re: [sqlite] how often to open the db

On Mon, Jun 21, 2010 at 10:44 PM, Sam Carleton wrote: > I have asked this Q a number of times over the last year and NEVER gotten > ANYONE to even comment on it.  I am wondering why: > > Am I opening the DB too much? what is too much? I mean, the computer is not going

[sqlite] how often to open the db

I have asked this Q a number of times over the last year and NEVER gotten ANYONE to even comment on it. I am wondering why: Am I opening the DB too much? My usage of SQLite is in an Apache module that opens the DB each time it needs info from the DB: For authentication it is open/closed, for

[sqlite] Error in date.test with encryption codec

The date14 test uses hexio_write, which is invalid when opened with an encryption codec Regards, Noah Hart -- View this message in context: http://old.nabble.com/Error-in-date.test-with-encryption-codec-tp28953028p28953028.html Sent from the SQLite mailing list archive at Nabble.com.

[sqlite] Error in pagesize.test with encryption codec

pagesize returns incorrect results when using a codec with an encryption routine, since the Vacuum is not allowed to change the page size of an encrypted database Suggested changes, change the test to open the databases without encryption by adding -key {} to all the sqlite3 db test.db

[sqlite] Error in exclusive2.test with encryption codec

exclusive2returns incorrect results when using a codec with an encryption routine, since the pagerChangeCounter reads directly from the file Suggested changes, run the test without encryption Line 23 +# Disable encryption on the database for this test. +sqlite3 db test.db -key {} Regards,

[sqlite] Error in nan.test with encryption codec

nan returns incorrect results when using a codec with an encryption routine, since test nan-3.1 reads directly from the file via hexio_read test.db 2040 8 Suggested changes, run the test without encryption, or skip test 14 when running with a codec line 27: +# Disable encryption on the

[sqlite] Error in pcache.test with encryption codec

pcachereturns incorrect results when using a codec with an encryption routine, since test pcache-1.14 writes directly to offset 24 in the header Suggested changes, run the test without encryption, or skip test 14 when running with a codec line 31: - sqlite3 db test.db +sqlite3 db test.db -key

[sqlite] Error in vacuum2.test with encryption codec

vacuum2 returns incorrect results when using a codec with an encryption routine Suggested changes: line 31: +# Disable encryption on the database for this test. sqlite3 db test.db -key {} Change line 70 - sqlite3 db2 test.db +sqlite3 db2 test.db -key {} Noah Hart -- View this

[sqlite] Error in filefmt.test with encryption codec

filefmt return incorrect results when using a codec with an encryption routine filefmt-1.1... Expected: [53514C69746520666F726D6174203300] Got: [19C10CA15F9AB24A612E680FE7816B25] This happens because the sqlite db command in TCL opens the database with the option -key {xyzzy} when compiled

[sqlite] Error in jrnlmode2.test with encryption codec

jrnlmode2-2.4 & 2-2.6, return incorrect results when using a codec with an encryption routine Expected: [0 {1 2 3 4 5 6}] Got: [1 {file is encrypted or is not a database}] This happens because the sqlite db command in TCL opens the database with the option -key {xyzzy} # Use the pager codec

[sqlite] Error in minmax3.test with SQLITE_HAS_CODEC

minmax3.test has a routine at line 23 # This procedure sets the value of the file-format in file 'test.db' # to $newval. Also, the schema cookie is incremented. # proc set_file_format {newval} { hexio_write test.db 44 [hexio_render_int32 $newval] set schemacookie [hexio_get_int [hexio_read

Re: [sqlite] When to close a db?

On Mon, Jun 21, 2010 at 12:24 PM, Roger Binns wrote: > > On 06/21/2010 08:44 AM, Sam Carleton wrote: > > I know I cannot afford ... > > For some reason you are assuming that your time is free and that you have > no > other things to do with it (opportunity cost). That is

Re: [sqlite] Oracle joins the SQLite Consortium

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/21/2010 04:47 AM, Igor Sereda quoted Oracle: >> The application-level behavior of the two products is identical, I did test the Oracle version a few months ago and found that statement to be false. Oracle know about the issues but gave the

Re: [sqlite] When to close a db?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/21/2010 08:44 AM, Sam Carleton wrote: > I know I cannot afford ... For some reason you are assuming that your time is free and that you have no other things to do with it (opportunity cost). That is how you should be weighing all of this. And

Re: [sqlite] Oracle joins the SQLite Consortium

On Mon, Jun 21, 2010 at 04:47:12AM -0700, Igor Sereda wrote: > > Wow, that's interesting news. Berkeley DB is still GPL/commercial, I guess? I > hope SQLite will keep on going under public domain, including its B-tree > level. > > Also, here's an interesting statement in the BDB/SQLite

Re: [sqlite] When to close a db?

On Mon, Jun 21, 2010 at 11:29 AM, Pavel Ivanov wrote: >> hopefully there are better tools there for debugging this >> type of thing. > > There are, but usually they are not free. Quick googling for "valgrind > for windows" brought up commercial products Purify and Insure++ and

Re: [sqlite] When to close a db?

> hopefully there are better tools there for debugging this > type of thing. There are, but usually they are not free. Quick googling for "valgrind for windows" brought up commercial products Purify and Insure++ and free product DUMA. I used Purify myself occasionally - it's not bad, but you have

Re: [sqlite] When to close a db?

On Mon, Jun 21, 2010 at 9:37 AM, Roger Binns wrote: > As an example you would experience something like this if SQLite got > initialized during the config phase. Just to make things even more > complicated ASLR is turned off if you have Wine installed under Linux so I >

Re: [sqlite] Question About SQLITE and AIR efficiency

Does you query involve LIKE? That has been overriden in AIR so it won't make use of an index. If your queries permit, use GLOB instead. I have used SQLite with Adobe AIR without any performance problems/slowness other than the one above relating to LIKE. N.B. If your database was designed

Re: [sqlite] When to close a db?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/20/2010 08:31 PM, Sam Carleton wrote: > So, that seems to leave a memory error in my code, which is also very > tough to find. All the code that is blowing up is within an Apache > Module and I am following the Apache rules very closely. To

[sqlite] Yet another SQLite wrapper for C++

hi,   i've written a small (<100 lines) c++ wrapper for sqlite. it supports:  *) prepared statements  *) NULL  *) BLOBs   here is a small usage example: ---SDB sdb("test.sdb");

Re: [sqlite] Oracle joins the SQLite Consortium

Wow, that's interesting news. Berkeley DB is still GPL/commercial, I guess? I hope SQLite will keep on going under public domain, including its B-tree level. Also, here's an interesting statement in the BDB/SQLite announcement: > Thus, applications written to the SQLite version 3 API can

Re: [sqlite] Oracle joins the SQLite Consortium

Question also. Can one trust that when you look at what those folks are doing to SMI, or whatever they are called now. -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Simon Slavin Sent: Monday, June 21, 2010 5:31 AM To:

Re: [sqlite] Oracle joins the SQLite Consortium

On 21 Jun 2010, at 12:10pm, Francisco Azevedo wrote: > On 21-06-2010 11:58, D. Richard Hipp wrote: >> guarantees that SQLite will continue to be actively maintained and >> developed and that it will not fall under the control of a competitor. > > Sorry, but.. isn't oracle the "competitor" ? :)

Re: [sqlite] Oracle joins the SQLite Consortium

On 21-06-2010 11:58, D. Richard Hipp wrote: > guarantees that SQLite will continue to be actively maintained and > developed and that it will not fall under the control of a competitor. Sorry, but.. isn't oracle the "competitor" ? :) Francisco A ___

Re: [sqlite] Fwd: A DLL for my WinXP

You also can search Google "sqlite dll download" and follow the first hit ... Am 21.06.2010 12:56, schrieb Arbol One: > Helloo! is any body there??!! > nock nock ... Is this group dead??!! > > Where can I find the DLL file for my winxp? > TIA > > > > Original Message >

Re: [sqlite] Fwd: A DLL for my WinXP

Here: http://www.sqlite.org/sqlitedll-3_6_23_1.zip Am 21.06.2010 12:56, schrieb Arbol One: > Helloo! is any body there??!! > nock nock ... Is this group dead??!! > > Where can I find the DLL file for my winxp? > TIA > > > > Original Message > Subject: A DLL for my WinXP

[sqlite] Oracle joins the SQLite Consortium

The SQLite developers are pleased to announce that Oracle has joined the SQLite Consortium. The SQLite Consortium is a collaboration of major users of SQLite designed to ensure the continuing vitality and independence of SQLite. In exchange for sponsorship, SQLite Consortium Members

[sqlite] Fwd: A DLL for my WinXP

Helloo! is any body there??!! nock nock ... Is this group dead??!! Where can I find the DLL file for my winxp? TIA Original Message Subject:A DLL for my WinXP Date: Sun, 20 Jun 2010 20:59:20 -0400 From: Arbol One To:

Re: [sqlite] When to close a db?

Sam, Could it be that you have prepared statements still active when you're trying to close the db? (not finalized, that is) -- Tito Sent from my iPhone On 20 Jun 2010, at 23:17, Sam Carleton wrote: > I am getting some strange behavior out of my app, which

Re: [sqlite] When to close a db?

Some time ago, I had a similar error because included a reference to a pointer sqlErrMsgPtr = (CHAR *) sqlite3_errmsg (dbPtr) in my SQLite class destructor. As someone has suggested, does look to be associated with a dangling pointer. HTH A.J. Millan - Original Message - From: