From: | mgould <mgould(at)allcoast(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Possible new feature |
Date: | 2007-07-30 12:02:29 |
Message-ID: | 20070730120229.f24af0db@mail.allcoast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
All,
I'm in the process of moving to PostGres from iAnywhere's SQL Anywhere v 10. One of the neat features from ASA 10 is the ability to create "proxy tables" These tables can be local or remote. The purpose of a proxy table is that once create it can be used just like any other table or view. You can use it in joins, subselects, etc. ASA sees it as just a normal table. The data can be stored in any ODBC compatible file system so it makes it easy to interact with all other database. The synatx is pretty simple :
CREATE EXISTING TABLE [owner.]table-name
[ (column-definition, ...) ]
AT location-string
column-definition :
column-name data-type [NOT NULL]
location-string :
remote-server-name.[db-name].[owner].object-name
| remote-server-name;[db-name];[owner];object-name
example:
CREATE EXISTING TABLE blurbs
( author_id ID not null,
copy text not null)
AT 'server_a.db1.joe.blurbs';
Now you can acces blurbs just like any table.
Best Regards,
Michael Gould
All Coast Intermodal Services Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Lewis Cunningham | 2007-07-30 12:22:38 | Re: [SQL] Tunning PostgreSQL performance for views on Windows |
Previous Message | Alban Hertroys | 2007-07-30 10:27:45 | Re: query to match '\N' |