SQL only creates indexes on the fly in very specific circumstances so most
of the time, you'll get a serial scan if your'e selecting on a column that
is not indexed. You can use the EXPLAIN QUERY PLAN statement to find out
exactly how any given SELECT statement is processed by sqlite.
Even if you
On 5/31/12 9:35 PM, "Bob Sneidar" wrote:
> Yes, but it is my understanding of SQL that a query on a non-indexed column
> will create a temporary index in mySQL and maybe others.
I do not think so ...
Look. To build index db engine need read all values of column yes?
and yet build the whole inde
Yes, but it is my understanding of SQL that a query on a non-indexed column
will create a temporary index in mySQL and maybe others. I might be wrong about
that. But Foxpro does not do that. In fact if you set a filter or seek using a
FOR statement that has no indexed columns or has some non-ind
On 5/31/12 8:14 PM, "Bob Sneidar" wrote:
> Foxpro does, but it's slow.
You mean that foxpro can do
search on column that is not indexed ?
Well, of course each db engine can do this. :-)
And Valentina, and Light, and mySQL, ...
And yes it is much slower than indexed search,
I did mean bel
Foxpro does, but it's slow.
Bob
On May 31, 2012, at 9:57 AM, Ruslan Zasukhin wrote:
>> Additionally, the structure of an SQLite DB, particularly the indexing,
>> can radically improve performance.
>
> Not very right.
>
> Any db have indexing. And relational, and navigational, and columnar.
On 5/31/12 5:47 PM, "Richard Gaskin" wrote:
Hi Richard,
>> The sql statements were not that complex, just a LOT of toing and froing
>> between LC and the db. I soon abandoned SQLite as it was clear that
>> Valentina was getting the answers quicker.
>
> Ruslan's genius is noteworthy, but perhaps
