Hello,
The SQL-MED specification defines the IMPORT FOREIGN SCHEMA statement.
This adds discoverability to foreign servers. The structure of the statement
as I understand it is simple enough:
IMPORT FOREIGN SCHEMA remote_schema FROM SERVER some_server [ (LIMIT TO |
EXCEPT) table_list ] INTO
On Fri, Feb 21, 2014 at 4:01 PM, Ronan Dunklau ronan.dunk...@dalibo.comwrote:
Hello,
The SQL-MED specification defines the IMPORT FOREIGN SCHEMA statement.
This adds discoverability to foreign servers. The structure of the
statement
as I understand it is simple enough:
IMPORT FOREIGN
I havent had a look at the patch yet since I dont have a nice editor right
now, but how do you handle inter operability between datatypes?
Specifically, how do you handle those datatypes which have a different name
from the PostgreSQL name for them and/or are stored in a different manner?
Do
On Fri, Feb 21, 2014 at 4:39 PM, Ronan Dunklau ronan.dunk...@dalibo.comwrote:
I havent had a look at the patch yet since I dont have a nice editor
right
now, but how do you handle inter operability between datatypes?
Specifically, how do you handle those datatypes which have a different
Le vendredi 21 février 2014 16:45:20 Atri Sharma a écrit :
On Fri, Feb 21, 2014 at 4:39 PM, Ronan Dunklau
ronan.dunk...@dalibo.comwrote:
I havent had a look at the patch yet since I dont have a nice editor
right
now, but how do you handle inter operability between datatypes?
On Fri, Feb 21, 2014 at 4:56 PM, Ronan Dunklau ronan.dunk...@dalibo.comwrote:
Le vendredi 21 février 2014 16:45:20 Atri Sharma a écrit :
On Fri, Feb 21, 2014 at 4:39 PM, Ronan Dunklau
ronan.dunk...@dalibo.comwrote:
I havent had a look at the patch yet since I dont have a nice editor
On Feb21, 2014, at 12:09 , Ronan Dunklau ronan.dunk...@dalibo.com wrote:
I havent had a look at the patch yet since I dont have a nice editor right
now, but how do you handle inter operability between datatypes?
Specifically, how do you handle those datatypes which have a different name
from
Who says that the OIDs are the same on the local and the remove postgres
instance? For user-defined types, that's certainly not going to be true...
That's why the the result is casted as regtype[], and parsed as such. The oid
is not transmitted over the wire, but set by regtype_in.
Also,