Received: from jasmine.cloudband.com (jasmine.cloudband.com [195.112.56.203]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA43768 for ; Mon, 6 Sep 1999 09:56:34 -0400 (EDT) (envelope-from erice@cloudband.com) Received: from cloudband.com (IDENT:root@linux1.dev.net [195.149.6.10]) by jasmine.cloudband.com (8.9.2/8.9.2) with ESMTP id OAA13754 for ; Mon, 6 Sep 1999 14:56:33 +0100 (BST) Sender: root@jasmine.cloudband.com Message-ID: <37D3D6A8.E83703E5@cloudband.com> Date: Mon, 06 Sep 1999 14:58:48 +0000 From: Eric Enockson Reply-To: erice@cloudband.com Organization: cloudband.com X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: creating indexes on character fields Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by hub.org id JAA43791 i have a person here who is telling me that i should not create indexes on character fields. That is a index_field char(32) or something. This doesn't make sense to me because it seems that we can order strings as easily as ordering numbers as they're all just binary to the computer anyway. He is saying bascially that this bit off code from my sql book is something he has never seen done in a database in his life. I do not understand. Create INDEX author_name on books (author_name)