Re: [sqlite] Using indexed fields in a table.

On Sat, Mar 5, 2011 at 8:14 AM, BareFeetWare wrote: > On 05/03/2011, at 1:59 AM, "J Trahair" > wrote: > > > I understand about Primary keys and Unique keys attributed to their own > field. Is there a need to have other fields indexed,

Re: [sqlite] Using indexed fields in a table.

On 05/03/2011, at 1:59 AM, "J Trahair" wrote: > I understand about Primary keys and Unique keys attributed to their own > field. Is there a need to have other fields indexed, for faster searching? > Eg. a table containing your favourite music. Say you have 9

Re: [sqlite] Using indexed fields in a table.

On 4 Mar 2011, at 2:59pm, J Trahair wrote: > You have a table called AllMusic containing columns called Composer, > NameOfPiece, YearComposed, etc. > > SELECT * FROM AllMusic_tbl WHERE Composer = 'Bach' ORDER BY YearComposed > > I thought the select would be quicker if the AllMusic table had

[sqlite] Using indexed fields in a table.

Hi I understand about Primary keys and Unique keys attributed to their own field. Is there a need to have other fields indexed, for faster searching? Eg. a table containing your favourite music. Say you have 9 Beethoven symphonies (one row in the table for each), 14 Bach partitas and 100 Haydn