Received: from eater.zotnet.com (IDENT:root@snapuser87.pacificcrest.net [216.36.24.87]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA57195 for ; Sat, 24 Jul 1999 14:35:52 -0400 (EDT) (envelope-from zot@ZotConsulting.com) Received: from ZotConsulting.com (snapuser115.pacificcrest.net [216.36.24.115]) by eater.zotnet.com (8.8.7/8.8.7) with ESMTP id MAA26055 for ; Sat, 24 Jul 1999 12:14:27 -0700 Message-ID: <379A0DB9.AA330EA4@ZotConsulting.com> Date: Sat, 24 Jul 1999 12:02:17 -0700 From: "Zot O'Connor" Organization: Zot Consulting X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: postgres sql Subject: Coverting mysql keys Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Excuse my complete ignorance of SQL. I am converting a mysql DB to postgres. Mysql defines keys in the Create table structure like: create table ohead ( custid varchar(8), key orderid (orderid), ..... To covert this to postgres I guess I need an index, which is done externally to the create table? : create table ohead ( custid varchar(8), orderid (orderid), ... CREATE INDEX orderid(??use same name or _idx??) on ohead (orderid); Again, I am clueless to SQL, how do I utilize the increase in speed? Does it happen when I SELECT/JOIN things together? or do I reference the index in my queries. Thanks! -- Zot O'Connor www.ZotConsulting.com www.WhiteKnightHackers.com