4 ms·
> As for whether they're a secret weapon? Well, they're not so secret, but it does seem like they're underutilized considering the power they grant. We certainl
by sradman 6y ago
> As for whether they're a secret weapon? Well, they're not so secret, but it does seem like they're underutilized considering the power they grant. We certainly like them.
They are indeed powerful and underutilized. They also go by different names in other RDBMSes (proxy tables, linked servers, remote tables, virtual tables, etc.). If I remember correctly, SQL Anywhere 6 released in 1998 was the first rich implementation [1] of "proxy tables" to "remote servers" and Microsoft soon followed with "Linked Servers". The embedded database libraries (Apache Derby and SQLite) added rich APIs/SPIs to create virtual table plugins like SQLite's FTS.
Using remote tables for federated queries across heterogenous data sources, and for access to non-relational data sources, is a well established technique and a powerful "weapon" for those who know how to wield it. It might not be PostgreSQL's secret weapon but it may very well be Splitgraph's.
[1] http://dcx.sap.com/index.html#1001/en/dbwnen10/wn-remote-new601.html http://dcx.sap.com/index.html#1001/en/dbwnen10/wn-remote-new...
- jungturk 6y agoRight. In AWS Redshift-land, this feature is called Spectrum, and allows you to use the redshift query engine & its SQL support to access external data (say, parquet files on S3).
- ako 6y agoI think oracle had database links before 1998 which enables you to have proxy tables for tables in other oracle databases.
- sradman 6y agoIt looks like Oracle had CREATE DATABASE LINK since at least 7.3 [1] in 1996 (probably earlier too but I couldn't find when it was introduced). It wasn't Oracle-only either: > However, to access non-Oracle systems you must use Oracle Heterogeneous Services. [1] https://docs.oracle.com/cd/A57673_01/DOC/server/doc/SQL73/ch4a.htm#toc087 https://docs.oracle.com/cd/A57673_01/DOC/server/doc/SQL73/ch...