Re: [sqlite] beat 120,000 inserts/sec

2005-04-09 Thread bbum
On Apr 9, 2005, at 8:49 AM, Al Danial wrote: I did try SYNCHRONOUS=off but that didn't seem to have an effect; I'll study the docs to make sure I've got it right. This isn't surprising. fsync() is largely a no-op on just about any operating system. It doesn't actually guarantee that the bytes

Re: [sqlite] beat 120,000 inserts/sec

2005-04-09 Thread bbum
There are also pragmas to control page size and in-memory caching. You will want to play with those, as well. If SQLite is in the middle of a transaction and you load it up with commands, it will create a journal file in /tmp/ to start pages that don't fit in the in-memory page cache (or

Re: [sqlite] No password to protect the sqlite database file

2005-04-02 Thread bbum
On Apr 2, 2005, at 5:32 PM, liigo wrote: Thanks, but why not sqlite add a password to the database file? There isn't much value in adding a password required to access the file. The user could still easily see all of the data stored within the SQLite file. SQLite is an embedded database file.

Re: [sqlite] test errors on OSX

2005-04-01 Thread bbum
On Apr 1, 2005, at 11:10 AM, Stephen C. Gilardi wrote: For several months now, I've gotten similar errors when I run the test on my PowerBook G4. For me, the set of tests that fail is different from test run to test run, but they do seem to be concentrated in the "*ioerr" tests for the most

Re: [sqlite] SQLite v3.1.4 - Mac OS X 10.3.8 compile issues

2005-03-11 Thread bbum
On Mar 11, 2005, at 8:09 AM, Eric Hochmeister wrote: I just noticed that a new version of SQLite 3.1.4 was up, so I downloaded it and can't seem to get it to compile. I have successfully been using previous versions of SQLite (3.1.3, 3.0.8, etc.) and this is the first time I've received an issue

Re: [sqlite] sluggish operation on os x?

2005-02-21 Thread bbum
On Feb 21, 2005, at 11:44 AM, Curtis King wrote: On 21-Feb-05, at 11:11 AM, [EMAIL PROTECTED] wrote: OK -- so, you are willing to accept the risk of non-recoverable database corruption in the event of power outage or other kinds of catastrophic system failure (including the plug being pulled on

Re: [sqlite] sluggish operation on os x?

2005-02-21 Thread bbum
On Feb 21, 2005, at 9:54 AM, James Berry wrote: On Feb 21, 2005, at 9:40 AM, Curtis King wrote: I noticed this as well, so I profiled my call and found sync was taking forever. I removed the following fcntl call, rc = fcntl(fd, F_FULLFSYNC, 0);. Performance was back to normal. Here are some

Re: [sqlite] Python bindings for SQLite 3?

2005-02-17 Thread bbum
On Feb 17, 2005, at 9:53 AM, H. Wade Minter wrote: I'm playing around with some Python stuff, and was wondering if there were any reasonably stable bindings for SQLite 3? I've got an existing SQLite 3 database that I want to work against, so I'd rather not drop back to SQLite 2? I have been

Re: [sqlite] sqlite & multithreading

2005-02-07 Thread bbum
On Feb 7, 2005, at 10:21 AM, Alex Chudnovsky wrote: Correct me if I am wrong but I was under the impression that having 2 separate connections to database (and while on subject I noticed that making connection via ADO.NET takes significant time measured in seconds rather than in milliseconds)

Re: RE(1): [sqlite] SQLite Advocacy

2005-01-31 Thread bbum
On Jan 31, 2005, at 9:31 AM, [EMAIL PROTECTED] wrote: Not true at all. In fact, from experience, the Linux OS is much more full of holes than Windows. It appears most hate Microsoft so thier OS gets the most virus and hackers. All I can say is we independently did a test with Linux and

Re: [sqlite] few questions...

2005-01-23 Thread bbum
On Jan 23, 2005, at 8:11 AM, Jason Morehouse wrote: We are currently using mysql. What is the comparison to opening a database with sqlite vs connecting to the daemon with mysql? Our current box has seen 300+ connections to the sql server at at once. Can we expect that having 300 databases

[sqlite] tcl_install ignores DESTDIR

2005-01-21 Thread bbum
The 'tcl_install' target of Makefile.in ignores the DESTDIR that may have been specified as a part of the build. The tclinstaller.tcl script should install the sqlite3 tcl hook in DESTDIR/LIBDIR such that a build-for-packaging doesn't inadvertently shove things into the installed system. The

Re: [sqlite] 3.1 vs. 3.0 file compatibility.

2005-01-21 Thread bbum
On Jan 21, 2005, at 2:49 PM, Dan Kennedy wrote: If the 3.1 file is created with the auto-vacuum option enabled ("PRAGMA auto_vacuum = 1;"), then the database will appear read-only to 3.0 clients. That's the only incompatibility. OK -- can auto-vacuum be turned on within a database that was created

[sqlite] 3.1 vs. 3.0 file compatibility.

2005-01-21 Thread bbum
Under what circumstances is a file written by 3.1 incompatible with a file written by 3.0? thanks, b.bum smime.p7s Description: S/MIME cryptographic signature

Re: [sqlite] possible workaround for bug #301

2005-01-19 Thread bbum
On Jan 19, 2005, at 10:43 AM, Will Leshner wrote: Bug #301 says that, because fcntl isn't supported for remove volumes on OS X, SQLite can't acquire a lock, which, I think, pretty much means you can't use SQLite databases that are on AFP or SMB volumes on OS X. What would happen if I simply made

Re: [sqlite] Mac OS X and SQLite Locking

2005-01-04 Thread bbum
On Tue, 4 Jan 2005, Steve Milner wrote: Hello List, I am having a problem with SQLite erroring out on Mac OS X. I am using 3.0.8. The problem happens when it tries to access a SAMBA/CIFS shared database. In my testing Windows to Linux and Linux to Windows worked fine, but Mac to Windows

Re: [sqlite] VACUUM function problem

2004-12-28 Thread bbum
On Dec 28, 2004, at 11:44 AM, D.W. wrote: Is there a function that does what I have described? [described... 'compact' the primary keys of a database so that there are no unused gaps after a row or rows have been deleted] No. And, generally, you really don't want to do that. The primary keys

Re: [sqlite] Large memory usage not freed?

2004-11-04 Thread bbum
On Nov 4, 2004, at 3:42 PM, D. Richard Hipp wrote: If we exit the process and then reopen the database in a new process, all that memory is not reallocated. Are you sure you have that right? What OS are you running? Also, how are you checking to see if the memory was deallocated in the first