-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 29 Jan 2002, Rodolfo J. Paiz wrote: >If it's a small database, I'd go for the fingerprint; if it's fairly >large, then studying the overhead versus the bulk is important. Don't >know enough about tuning to help you, though; just know that whoever >*can* help you is going to need more info.
I would recommend just the opposite. If the database is small, the calculation would be a waste of time. Just index the whole key. If the database is large, the time lost in calculation woudl be made in in search speed. Now all you have to do is figure out where "small" ends and "large" begins. ;-) I'd say that actual tests are the only way to get answers that apply to your application. Tony - -- Anthony E. Greene <[EMAIL PROTECTED]> <http://www.pobox.com/~agreene/> PGP Key: 0x6C94239D/7B3D BD7D 7D91 1B44 BA26 C484 A42A 60DD 6C94 239D Chat: AOL/Yahoo: TonyG05 Linux. The choice of a GNU generation <http://www.linux.org/> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Anthony E. Greene <[EMAIL PROTECTED]> 0x6C94239D iD8DBQE8V4/rpCpg3WyUI50RAjC2AKDywfME3ftJ+8ZKOn8u3usjxE9UcACeNM4V J2LbnVNdTy3g+q63eHHFyAQ= =qL1+ -----END PGP SIGNATURE----- _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
