The keyfield should probably be PRIMARY KEY. But what about the lockfield? Should it be indexed at all? And if so, using UNIQUE or just INDEX? It will usually not hold that many values at the same time and it alters with high frequency. Writing to it will slow down using an index but will searching speed up? In a table with several thousands of records maybe only 1-20 users are actually editing a record at a given time. Would an index help here?
HDB Jolle
-- ############################################################# This message is sent to you because you are subscribed to the mailing list <knop@lists.montania.se>. To unsubscribe, E-mail to: <knop-off@lists.montania.se> Send administrative queries to <knop-request@lists.montania.se> List archive http://www.nabble.com/Knop-Framework-Discussion-f29076.html Project homepage http://montania.se/projects/knop/ Google Code has the latest downloads at http://code.google.com/p/knop/
Nov 13
Johan Solve Re: Proper use of indexing
Nov 13, 2008; 07:32
Johan Solve
Re: Proper use of indexing
Nov 13
Jolle Carlestam Re: Proper use of indexing
Nov 13, 2008; 08:24
Jolle Carlestam
Re: Proper use of indexing
Search
Lasso Programming
This site manages and broadcasts several email lists pertaining to Lasso Programming and technologies related and used by Lasso developers. Sign up today!