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
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@wareonearth.com]
Sent: Thursday, April 15, 1999 6:15 AM
To: pgsql-general@postgreSQL.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
Import Notes
Resolved by subject fallback
If anyone's interested, it turns out a good temporary fix to this
problem involves only two lines of SQL:
update pg_class set relname = lower(relname);
update pg_attribute set attname = lower(attname);
This seems to work without any side effects. enjoy- glenn
Show quoted text
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
Import Notes
Resolved by subject fallback
Hello all,
My database seems to be functioning much slower than I would expect of
even the worst database. Can anyone point me towards any fine tuning
that I can do(i.e. documentation, web sites, comentary).
Thanks Very Much.
Can I assume you have been regularly vaccuming?
-----Original Message-----
From: Christopher Hutton <crhutton@welcomecard.com>
To: pgsql-general@postgreSQL.org <pgsql-general@postgreSQL.org>
Date: Thursday, April 15, 1999 3:12 PM
Subject: [GENERAL] Database performance
Show quoted text
Hello all,
My database seems to be functioning much slower than I would expect of
even the worst database. Can anyone point me towards any fine tuning
that I can do(i.e. documentation, web sites, comentary).Thanks Very Much.
Import Notes
Resolved by subject fallback
No, I have not. I will try that. Thanks. I don't know if that will help
though, because at this point none of my tables have more than about 50
rows.
K.T. wrote:
Can I assume you have been regularly vaccuming?
-----Original Message-----
From: Christopher Hutton <crhutton@welcomecard.com>
To: pgsql-general@postgreSQL.org <pgsql-general@postgreSQL.org>
Date: Thursday, April 15, 1999 3:12 PM
Subject: [GENERAL] Database performanceHello all,
My database seems to be functioning much slower than I would expect of
even the worst database. Can anyone point me towards any fine tuning
that I can do(i.e. documentation, web sites, comentary).Thanks Very Much.
--
Christopher Hutton
(847) 265-2028
"PocketCard, the best way to carry money"
Please visit www.pocketcard.com to learn more