Re: [sqlite] Re indexing (if such a thing exist) performance

On 24 Aug 2011, at 1:49pm, LiranR wrote: > I meant that the two PK columns are actually primary key of (id, > timestamp).. Okay. That's probably not what you want to do. If you think about your data you probably want just one of them as the primary key. The only way you would need both of th

Re: [sqlite] Re indexing (if such a thing exist) performance

Thanks... I meant that the two PK columns are actually primary key of (id, timestamp).. What i don't understand, is why do i need primary keys as timeStamp if not to make an index tree of my table rows ? Does the PK doesn't build an index tree of the rows so i can get a row faster? Simon Slavin-

Re: [sqlite] Re indexing (if such a thing exist) performance

On 24 Aug 2011, at 12:39pm, LiranR wrote: > ID (PK) | TimeStamp (PK) | data | data | and data ... > - >1 |101| float | float | float >2 |102| float | float | f

Re: [sqlite] Re indexing (if such a thing exist) performance

Systems Advanced Analytics Directorate From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of LiranR [liran.rit...@gmail.com] Sent: Wednesday, August 24, 2011 6:55 AM To: sqlite-users@sqlite.org Subject: EXT :Re: [sqlite] Re indexing (

Re: [sqlite] Re indexing (if such a thing exist) performance

> From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on > behalf of LiranR [liran.rit...@gmail.com] > Sent: Wednesday, August 24, 2011 6:39 AM > To: sqlite-users@sqlite.org > Subject: EXT :Re: [sqlite] Re indexing (if

Re: [sqlite] Re indexing (if such a thing exist) performance

AM To: sqlite-users@sqlite.org Subject: EXT :Re: [sqlite] Re indexing (if such a thing exist) performance I use: ID (PK) | TimeStamp (PK) | data | data | and data ... - 1 |101 | float |

Re: [sqlite] Re indexing (if such a thing exist) performance

bject: EXT :Re: [sqlite] Re indexing (if such a thing exist) performance I use: ID (PK) | TimeStamp (PK) | data | data | and data ... - 1 |101 | float | float | float 2 |

Re: [sqlite] Re indexing (if such a thing exist) performance

rs-boun...@sqlite.org] on behalf of LiranR [liran.rit...@gmail.com] Sent: Wednesday, August 24, 2011 4:58 AM To: sqlite-users@sqlite.org Subject: EXT :Re: [sqlite] Re indexing (if such a thing exist) performance Hi, Thanks for the answer, but i think you didn't understand what i asked. I use

Re: [sqlite] Re indexing (if such a thing exist) performance

I use: ID (PK) | TimeStamp (PK) | data | data | and data ... - 1 |101 | float | float | float 2 |102 | float | float | float 3 | 3

Re: [sqlite] Re indexing (if such a thing exist) performance

On Wed, 24 Aug 2011 02:58:58 -0700 (PDT), LiranR wrote: > > Hi, Thanks for the answer, but i think you didn't understand what i asked. > > I use primary key index in my table. > When i finish to fill the table, row after row, i want to start all over > again and update the table from row 1 to row

Re: [sqlite] Re indexing (if such a thing exist) performance

ilar speed. Sumit -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of LiranR Sent: 24 August 2011 15:29 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Re indexing (if such a thing exist) performance Hi, Thanks for the answer, b

Re: [sqlite] Re indexing (if such a thing exist) performance

essage- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of LiranR > Sent: 24 August 2011 14:11 > To: sqlite-users@sqlite.org > Subject: [sqlite] Re indexing (if such a thing exist) performance > > > Hi all!! > In my proje

Re: [sqlite] Re indexing (if such a thing exist) performance

s. Sumit -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of LiranR Sent: 24 August 2011 14:11 To: sqlite-users@sqlite.org Subject: [sqlite] Re indexing (if such a thing exist) performance Hi all!! In my project, i insert rows, one by

[sqlite] Re indexing (if such a thing exist) performance

Hi all!! In my project, i insert rows, one by one, to a fixed size table (100 rows for example). When i reach the end of the table, i enter data to the first row and then the seocond and so on. If i have indexes (primary keys), lets say from 1 to 100, and now i reached the end, and update