Op 2010-07-01 12:50, Alan T het geskryf: > > I am also worry about the performance but now not the select but insert. > Since the way I generate the GUID like PK will not be sequentially increment > to the last record.
A OID (in tiOPF terms) has nothing to do with the actual data, so why treat it as such in the database. Use fields that have more "meaning" and sort by those when you retrieve data (and apply database optimisation on those fields too, like creating Indexes etc.). GUID's in this case is just as useless as an AutoInc field - they don't relate to the data at all, so I would never consider sorting by that field. Examples of other, more meaning full fields I would consider sorting on: * a contact's Lastname, Firstname. * a product code (a meaning full code inserted by the user) * a product description * a transaction date ... Regards, - Graeme - ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ tiOPF-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tiopf-talk
