Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: <plist@horistjr.com>, <pgsql-sql@postgresql.org>
Subject: Re: SQL Statements question, why I get errors...
Date: Sun, 23 Feb 2003 14:57:47 -0800
User-Agent: KMail/1.4.3
References: <1519.192.168.100.1.1046038673.squirrel@mail.horistjr.com>
In-Reply-To: <1519.192.168.100.1.1046038673.squirrel@mail.horistjr.com>
MIME-Version: 1.0
Message-Id: <200302231457.47596.josh@agliodbs.com>
Content-Transfer-Encoding: quoted-printable

"Plist,"

> I work a software company and our software is run on databases..  We have
> no problem using MS SQL, DB2, ect...  One of my customers wanted to try
> and use POSTGRESQL..  He tried it and is having problems, so I downloaded
> it and am running it on my Red Hat 7.3 box..  I am running version 7.3.2
> of Postgresql..  I hope this is the right place to ask this..  When we
> first launch our program we create several tables...  Here is an example
> of one table we create:

You're in for a long, painful process if you think you can port a productio=
n=20
application to PostgreSQL (or between *any* two database platforms) without=
=20
an expert DBA.   Perhaps you should consider a consultant?

> create table test (f1 int, f2 char(30), f3 char(30), f4 char(30))
> create unique index itest on test (f1 asc)

Some databases (MSSQL) require seperate indexes for ascending (ASC) and=20
descending (DESC) sorts.  Postgresql does not; since 7.2.0, we have been ab=
le=20
to use the same index for both types of sorts.  As such, Postgresql does no=
t=20
support the "ASC" syntax in index creation.  Simply change your statement t=
o:

create unique index itest on test (f1);

... and it will work.

--=20
Josh Berkus
Aglio Database Solutions
San Francisco