By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,852 Members | 2,200 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,852 IT Pros & Developers. It's quick & easy.

Can I get rid of the schemas?

P: n/a
In itself, the schema thing in version 7.4 is a good thing, but I'm
migrating from a postgres/msacces combination in 7.2 to 7.4, and I'm not to
keen on every table in msacces appearing a public_<tablename>. Is there a
way to avoid this?
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
--- Gerwin Philippo <ge****@vernet.nl> wrote:
In itself, the schema thing in version 7.4 is a good
thing, but I'm
migrating from a postgres/msacces combination in 7.2
to 7.4, and I'm not to
keen on every table in msacces appearing a
public_<tablename>. Is there a
way to avoid this?


I believe not.

"schema1.mytable" and "schema2.mytable" are entirely
separate entities, even though they have the same
name. How else could they be distinguished, if not by
the schema qualification?

If you link from Access to tables in any other DBMS
that supports schemas (e.g. MS SQL Server), you will
find the same thing.

__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.