Re: [sqlite] Direct access of table data

an Mission Systems > > > > > > > > > > From: sqlite-users-boun...@sqlite.org on behalf of Nathan Biggs > > Sent: Fri 4/23/2010 7:50 AM > > To: General Discussion of SQLite Database > > Subject: Re: [sqlite] Direct access

Re: [sqlite] Direct access of table data

How long would it take to test using an index with 18 fields? Might not be crazy. Gerry On 4/23/10, Nathan Biggs wrote: > Max, thanks for the information. That will be very useful for other > table queries, but not for this one. For my table in questions there > are 18

Re: [sqlite] Direct access of table data

From: sqlite-users-boun...@sqlite.org on behalf of Nathan Biggs Sent: Fri 4/23/2010 8:05 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Direct access of table data Yes, I do use batch inserts. On 4/23/2010 8:56 AM, Black, Michael (IS) wrote

Re: [sqlite] Direct access of table data

/2010 7:50 AM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Direct access of table data > > > > Max, thanks for the information. That will be very useful for other > table queries, but not for this one. For my table in questions there > are 18 fields.

Re: [sqlite] Direct access of table data

Northrop Grumman Mission Systems From: sqlite-users-boun...@sqlite.org on behalf of Nathan Biggs Sent: Fri 4/23/2010 7:50 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Direct access of table data Max, thanks for the information

Re: [sqlite] Direct access of table data

Max, thanks for the information. That will be very useful for other table queries, but not for this one. For my table in questions there are 18 fields. I think an index with 18 fields would be a little crazy. On 4/23/2010 3:06 AM, Max Vlasov wrote: > > > ...As I add more restrictions on the

Re: [sqlite] Direct access of table data

> ...As I add more restrictions on the where-clause it > tends to slow down. I realize that this is due to my indexes, but can't > add a lot of indexes because it slows down the insert speed which is > more important than the query speed. > Nathan, maybe you already knew but just in case... if

Re: [sqlite] Direct access of table data

Thanks for the input. Like everything else in life there are trade-offs. I guess that the real question originates because the time it takes to query the data seems a lot faster when I use a simplier select statement. As I add more restrictions on the where-clause it tends to slow down. I

Re: [sqlite] Direct access of table data

On Wed, Apr 21, 2010 at 1:19 PM, Nathan Biggs wrote: > Is there a way to read the values of a table directly without building > and executing a query.  I have a function that has predefined memory > (counters) and increments them if the data in the record matches a hard > coded

Re: [sqlite] Direct access of table data

> Since this is hard-coded, I thought it might perform much without all of > the memory allocations/de-allocations associated with the query engine. Don't use query engine then and store the information in separate file with your own hard-coded format. Pavel On Wed, Apr 21, 2010 at 2:19 PM,

Re: [sqlite] Direct access of table data

Hello Biggs, this is Griggs, Re: "Is there a way to read the values of a table directly without building and executing a query. I have a function that has predefined memory..." No easy way. The sophistication of database abstraction is the reason you presumably chose to use sqlite.

[sqlite] Direct access of table data

Is there a way to read the values of a table directly without building and executing a query. I have a function that has predefined memory (counters) and increments them if the data in the record matches a hard coded value. Since this is hard-coded, I thought it might perform much without all