RE: [GENERAL] case problem with MS Access export

From: Michael J Davis <michael(dot)j(dot)davis(at)tvguide(dot)com>
To: "'Glenn Waldron'" <gwaldron(at)wareonearth(dot)com>, pgsql-general(at)postgreSQL(dot)org
Subject: RE: [GENERAL] case problem with MS Access export
Date: 1999-04-15 16:29:38
Message-ID: 93C04F1F5173D211A27900105AA8FCFC1453C4@lambic.prevuenet.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

I have successfully exported my Access97 databases to PostgreSQL without the
case problem you describe. I have posted my notes and the Access97 database
I used to export my data in this web page:

www.sevainc.com/Access <http://www.sevainc.com/Access>

I did not use pgAdmin.

Thanks, Michael

-----Original Message-----
From: Glenn Waldron [SMTP:gwaldron(at)wareonearth(dot)com]
Sent: Thursday, April 15, 1999 6:15 AM
To: pgsql-general(at)postgreSQL(dot)org
Subject: [GENERAL] case problem with MS Access export

I've seen this question elsewhere on the list, but no good answer.
I am exporting large databases from MS Access to PG, but the table
and column names come out as case-sensitive in PG and I need to
quote them in order for PG to see them.

select * from table tab1;

gives an error because the table name is actually "TAB1", but SQL is
supposed to be case-insensitive. I understand that I can quote
everything and it will work, but this breaks tons of existing SQL
code.

Is there a better solution??? It would be nice for example, if
pgAdmin had such an option in its MS Access migration... -glenn

---
Glenn Waldron, WareOnEarth Inc. * v 703/847-2969 * f 703/847-2538

Browse pgsql-general by date

  From Date Subject
Next Message valter 1999-04-15 16:38:30 what is the MAX postgres db size & table size? NOBODY KNOWS?
Previous Message Martin Weinberg 1999-04-15 15:06:28 Performing a count(*) on a large table, how to optimize