On Oct 20, 2008, at 2:57 AM, Clodo wrote:
> Thanks for you answer MikeW.
>> Could you put the update records into their own separate table
> I already solved my problem using the newest "INDEXED BY".
> I'm trying to understand if is a SqLite limit or bug.
It's an unfortunate edge case alright.
> Hi Clodo,
>
> I believe Sqlite uses B-trees, unless one links in the R-tree module or
> uses the FTS feature (Full Text Search).
>
>
I don't know almost nothing about the internal implementation of a
database engine, i need to study to understand your reply :)
> I believe you wrote earlier
Hi Clodo,
I believe Sqlite uses B-trees, unless one links in the R-tree module or
uses the FTS feature (Full Text Search).
I believe you wrote earlier that the new "INDEXED BY" feature solved
your problem, but you saw something in the documentation that dissuaded
you. Do you mind saying just
Thanks for you answer MikeW.
>Could you put the update records into their own separate table
I already solved my problem using the newest "INDEXED BY".
I'm trying to understand if is a SqLite limit or bug.
And i'm trying to understand your answer about the hashes :(
For the moment, here you can
Fabrizio Carimati <[EMAIL PROTECTED]> writes:
>
> Hi to all,
> I have a table with many record, that have a field normally with value '0'.
> Occasionally i update some records by setting the field to '1' to mark
> it, and after in a background job, i localized them for working on it.
> For
Clodo wrote:
> Many thanks, it's a good news that resolve my problem.
>
> But still remain "a trick", i think the behaviour descripted in my
> original feedback is "strange".. i understand, if all fields have the
> same value, an index on that have a zero "height" in computing the best
>
Greetings, Clodo,
Regarding: "[is it]possible to force the use of the index?"
The very latest release of sqlite, 3.6.4, implements precisely that, in
the form of an "INDEXED BY" clause.
See:
http://www.sqlite.org/releaselog/3_6_4.html
Specifically:
Hi to all,
I have a table with many record, that have a field normally with value '0'.
Occasionally i update some records by setting the field to '1' to mark
it, and after in a background job, i localized them for working on it.
For that, i have an index on that field.
My problem: if i run an
Hi to all,
I have a table with many record, that have a field normally with value '0'.
Occasionally i update some records by setting the field to '1' to mark
it, and after in a background job, i localized them for working on it.
For that, i have an index on that field.
My problem: if i run an
Hello,
I would like to know more on the ANALYZE statement. The SQLite doc isn't very
clear on it.
We have some databases with large data in it. Running ANALYZE speeds up queries
in some databases, but not all.
What does it do exactly, what are the effects ? When do I have to run it ? How
much
10 matches
Mail list logo
