RE: [sqlite] Performance tuning using PRAGMA, other methods

I believe the optimizations that would help the most is the time spent on "commits." Thanks, Brett -Original Message- From: Scott Krig [mailto:[EMAIL PROTECTED] Sent: Thursday, November 29, 2007 10:57 AM To: sqlite-users@sqlite.org Subject: RE: [sqlite] Performance tuning using PRAGMA,

RE: [sqlite] Amalgamation questions

I couldn't find any docs or list emails regarding building the shell using the amalgamation, and things might change so that what I'm doing now may no longer "work." Thanks, Brett -Original Message- From: Brett Keating [mailto:[EMAIL PROTECTED] Sent: Saturday, June 09, 2007 9:43

[sqlite] Amalgamation questions

Hi, I am interested in upgrading my sqlite3, and the amalgamation looks like an interesting option. However I have some questions. 1) The page says with 3.3.18, the amalgamation will be available for direct download. Is 3.3.18 not available yet? It's not on the download page. If it's not I

RE: [sqlite] bizarre query problem

:41 AM To: sqlite-users@sqlite.org Subject: RE: [sqlite] bizarre query problem --- Brett Keating <[EMAIL PROTECTED]> wrote: > Msica independiente|text|19|0056_People Get Ready1_test1.wma > POP|text|3|0057_The Mighty Ship1_test1.wma 0058_The Mighty > POP|text|3|Quinn1_test1.wma >

RE: [sqlite] bizarre query problem

It said that the hex function was not found so I skipped that. Msica independiente|text|19|0056_People Get Ready1_test1.wma POP|text|3|0057_The Mighty Ship1_test1.wma POP|text|3|0058_The Mighty Quinn1_test1.wma Anyway, it turns out the problem was caused by creating an index on the genre field.

[sqlite] bizarre query problem

Hi, I have a bizarre problem. Here is an example of something I tried in sqlite3 3.3.8: sqlite> select genre,filename from objects where media_type=1; query abbreviated... Msica independiente|0056_People Get Ready1_test1.wma POP|0057_The Mighty Ship1_test1.wma POP|0058_The Mighty

RE: [sqlite] Effect of blobs on performance

Thanks I think this answers my question well! Brett -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 21, 2007 1:41 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Effect of blobs on performance "Brett Keating" <[EM

RE: [sqlite] Effect of blobs on performance

e. Thanks, Brett -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P Kishor Sent: Wednesday, February 21, 2007 1:38 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Effect of blobs on performance On 2/21/07, Brett Keating <[EMAIL PROTECTED]> wrot

RE: [sqlite] SQLite last inserted id

Can you use the API call sqlite3_last_insert_rowid ? -Original Message- From: Weston Weems [mailto:[EMAIL PROTECTED] Sent: Monday, January 22, 2007 3:58 PM To: sqlite-users@sqlite.org Subject: [sqlite] SQLite last inserted id What I'd ultimately like to do, and what I used to do with a

RE: [sqlite] Restricting integer primary key values

at open up a can of worms ? Wayne Brett Keating <[EMAIL PROTECTED]> wrote: Hi, This does indeed work, but only to prevent primary keys from being inserted into the database if they fall out of range. What I was hoping was that the with this command, the sqlite3 would always automaticall

RE: [sqlite] Restricting integer primary key values

. I will continue trying other things in the meantime. Thanks, Brett -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, January 14, 2007 6:09 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Restricting integer primary key values "Brett Keating&quo

RE: [sqlite] Restricting integer primary key values

Original Message----- From: Brett Keating [mailto:[EMAIL PROTECTED] Sent: Sunday, January 14, 2007 5:14 PM To: sqlite-users@sqlite.org Subject: [sqlite] Restricting integer primary key values Hi, I'm interested in the ability to restrict the values my integer primary key is allowed to take. Specifical

[sqlite] Restricting integer primary key values

Hi, I'm interested in the ability to restrict the values my integer primary key is allowed to take. Specifically, I would like to restrict the value to be between (but not including) 0x and 0x. In other words, a 32 bit number where all zeroes and all ones is not allowed. Is this