From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: relkind check in info.c |
Date: | 2014-05-15 07:41:56 |
Message-ID: | CAB7nPqR0apHpiPAi4J2e3oR2jZ8MREyJAzxdWMjrr4h5PsRp4w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On Wed, May 14, 2014 at 10:46 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> We need to decide to what to return in the table_type column for them.
> "FOREIGN TABLE" and "MATERIALIZED VIEW" would be natural choices.
This choice makes sense.
> But it would be good to return the same string that other DBMS's return for
> those things. What does SQL Server's driver return for materialized views?
> I'm not aware of any other DBMS that implements foreign tables per the spec,
> but e.g DB2 has "remote tables" and Oracle has "database links", which are
> similar features. I wonder what table type do they return.
Poking a little bit that, I finished with the patch attached, with
some regression tests attached. It may not be the most beautiful patch
ever, but it is consistent with the current way code is made and it
has the merit to be simple.
Regards,
--
Michael
Attachment | Content-Type | Size |
---|---|---|
0001-Add-support-for-foreign-tables-and-matviews.patch | text/plain | 8.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Itnal, Prakash (NSN - IN/Bangalore) | 2014-05-15 08:10:18 | Issue with retry_count in socket.c and fix for the same |
Previous Message | Michael Paquier | 2014-05-15 06:46:56 | Commit ad2a4ae causing more damages than fixes in regression tests |