I would like to maintain a sorted list of ~3000 entries.
I know that I can create a table and the SELECT from it with the ORDER BY clause
in order to sort it.
However I do not want the overhead of doing this after adding a new entry.
It would be good if I could create an index that was sorted,
This is very worrying since it means that the statement cannot be compiled on a
low memory device.
I am new to Sqlite, but I would guess that a precompiled query could be used,
where memory is low
and I also suppose that variable values could be bound to that precompiled
query.
Clive
I created an index on a TEXT column as I want to be able to
I noticed a large increase in the file size.
Looking at the binary of the file, I see that the index has a copy of all the
data being indexed.
1. Is this necassary?
2. Is there a way to keep the index only in memory and not in the
I am not an expert on indexes, however it does seem strange to me that a
database should keep duplicate data in it.
This prompted me to look up how indexes are stored in other databases. To tell
the truth I only looked at one, and that is SQL Server.
They do not store any duplicate data. If you
>From what I read SQL Server has 2 basic types of index:
1. Clustered, that holds the single instance of the data itself (actaully the
whole row)
2. Non-clustered that hold a pointer to the single instance of the data, but not
the data itself.
Clive
John Stanton <[EMAIL PROTECTED]> on
Actually yes, I am programming for a cellphone and you are right, that is the
only reason I am thinking about it!
Clive
"Griggs, Donald" <[EMAIL PROTECTED]> on 04/10/2007 21:23:17
Please respond to sqlite-users@sqlite.org
To: sqlite-users@sqlite.org
cc:(bcc: clive/Emultek)
Let's assume that my whole database can be in the cache. If my indexes have
duplicate data, then I will either need a bigger cache or have to page out row
data in favour of index data.
In that case it will either be slower or require more memory to keep duplicate
data for the indexes as opposed
sqlite3_step() is great for scrolling forward through a result set.
Is there a way to scroll backwards?
If not, did anyone try implementing it?
(I guess that the indexes would need backward pointers in order to do it.)
Clive
In the documentation below under the Pragmas section there seems to be a hint
that I can create a temporary index.
However the CREATE INDEX syntax does not allow the word TEMPORARY to be used.
Anyone know what is going on?
Clive
PRAGMA temp_store;
PRAGMA temp_store = DEFAULT; (0)
PRAGMA
9 matches
Mail list logo
