Message-ID: <1656.192.168.100.1.1046042001.squirrel@mail.horistjr.com>
Date: Sun, 23 Feb 2003 18:13:21 -0500 (EST)
Subject: Re: SQL Statements question, why I get errors...
From: <plist@horistjr.com>
To: <josh@agliodbs.com>
In-Reply-To: <200302231457.47596.josh@agliodbs.com>
References: <1519.192.168.100.1.1046038673.squirrel@mail.horistjr.com>
	<200302231457.47596.josh@agliodbs.com>
Importance: Normal
Cc: <plist@horistjr.com>, <pgsql-sql@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
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
> production  application to PostgreSQL (or between *any* two database
> platforms) without  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
> descending (DESC) sorts.  Postgresql does not; since 7.2.0, we have been
> able  to use the same index for both types of sorts.  As such,
> Postgresql does not  support the "ASC" syntax in index creation.  Simply
> change your statement to:
>
> create unique index itest on test (f1);
>
> ... and it will work.
>
I have tried that and yes it did work..  Just don't know if I want to tell
my programmers to go in change all there code for postgresql...  Thanks
for the info..

Ron

> --
> Josh Berkus
> Aglio Database Solutions
> San Francisco