Re: Migrating from MS-Access to Postgresql - Mailing list pgadmin-support

From Dave Page
Subject Re: Migrating from MS-Access to Postgresql
Date
Msg-id FED2B709E3270E4B903EB0175A49BCB129332F@dogbert.vale-housing.co.uk
Whole thread Raw
In response to Migrating from MS-Access to Postgresql  ("Marc Cuypers" <m.cuypers@pandora.be>)
List pgadmin-support
 
-----Original Message-----
From: Dino Nardini [mailto:dnardini@rivendellsoftware.com]
Sent: 28 March 2002 13:45
To: Dave Page; 'Marc Cuypers'; pgadmin-support@postgresql.org
Subject: Re: [pgadmin-support] Migrating from MS-Access to Postgresql

Hello,

I ran into similiar problems when migrating tables from MSSQL to Postgres.  Typically I create table names such as "TableName" and column names such as "TableID" in MSSQL.  If there exists a table called "TableName" and a column called "TableID" why won't the following query work in postgres:

SELECT TableID FROM TableName

I guess that my question is: why does Postgres muck around with the case?   Double quoting all tables and columns in a database that contains dozens of tables is far too much work, and I don't understand why I need to drop all my labels to lowercase in the DB.  Is there no way to override this behavior?
 
PostgreSQL is doing this as per the SQL spec (don't ask me what part, I'm just quoting what others have told me). You would get more knowledgable answers on one of the PostgreSQL lists - all I can really offer is advice on how pgAdmin can help you (by dropping the case or quoting).
 
Regards, Dave.

pgadmin-support by date:

Previous
From: Dino Nardini
Date:
Subject: Re: Migrating from MS-Access to Postgresql
Next
From: "Soundj - Skol Beats"
Date:
Subject: Soundj - Skol Beats