Scott Marlowe wrote:
How do you do cross db access within a transaction? You can't, and it's not likely that any code will be put in place todo this. But wasn't such code announced in 8.1? From http://www.postgresql.org/about/news.422 : "Two-Phase Commit (2PC): Long in demand for WAN applications and heterogeneous data centers using PostgreSQL, this feature allows ACID-compliant transactions across widely separated servers."
However I admit I don't know what end-user-level functionality 2PC has enabled in PG if any. From the announcement one might expect some equivalent of Oracle's database links, yet obviously we don't have this.
Even in Oracle you don't have cross db queries.
On the contrary you do. You can refer to objects in another database by [EMAIL PROTECTED], very useful to mix local and remote data in no time. DBLINK_NAME represents a connection to another database. What you don't have is OTHERDB.OBJECT_NAME to refer to a different database within the same instance, because there is only one database in an Oracle instance.
You use schemas there.
Also there are no real schemas in Oracle, or they're strictly tied from db users, and that's again quite different from how it's done in PG.
Regards, -- DanielPostgreSQL-powered mail user agent and storage: http://www.manitou-mail.org
-- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
