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
At 09:10 AM 28/03/2002 +0000, Dave Page wrote:
>Either change your query to:
>SELECT * FROM "Invoices"
>or, on the first step in the Migration Wizard, use the options to shift
>names to lower case, and re-migrate your data.
>Of course, if you only have a few tables/columns you could just rename
>them in pgAdmin.
>From: Marc Cuypers [mailto:m(dot)cuypers(at)pandora(dot)be]
>Sent: 28 March 2002 06:57
>Subject: [pgadmin-support] Migrating from MS-Access to Postgresql
>I migrated a few tables to postgresql. Everything migrated fine, but
>tablenames that contain capitals are converted just as is. When I create
>a query, postgresql doesn't seem to use those captitals and converts them
>to lowercase. This makes that the table is not found in the database and
>I get an error. I the database is a table 'Invoices', so the respons to
>the query 'select * from Invoices' is 'Relation invoices doesn't exist' .
>Can someone help me with this?
Rivendell Software - Dynamic Web Solutions
pgadmin-support by date
|Next:||From: Dave Page||Date: 2002-03-28 13:57:47|
|Subject: Re: Migrating from MS-Access to Postgresql|
|Previous:||From: Dave Page||Date: 2002-03-28 12:27:50|
|Subject: Re: Can't edit tables with timestamps|