SQL/MED

The SQL/MED ("Management of External Data") extension to the SQL standard is defined by ISO/IEC 9075-9:2008 (originally defined for SQL:2003). SQL/MED provides extensions to SQL that define foreign-data wrappers and datalink types to allow SQL to manage external data. External data is data that is accessible to, but not managed by, an SQL-based DBMS. This standard can be used in the development of federated database systems.

Implementations
  • PostgreSQL has support for some SQL/MED since version 9.1.[1][2]
  • LucidDB has support for SQL/MED.[3]
  • MariaDB has support for SQL/MED with the CONNECT storage engine.[4] The implementation uses different syntax than the official standard.
  • Farrago has support for SQL/MED.[5]
  • IBM DB2 has support for SQL/MED.[6]
  • Teiid has support for SQL/MED. [7]
gollark: Also, it doesn't, as tables are hashtables or whatever.
gollark: So what?
gollark: Removing the setfenving and passing the `environment` straight to `load` seems somehow to make it even more broken.
gollark: Doesn't work.
gollark: I have an environment table with new `fs` functions, and I want `loadfile` and `os.run` and whatever to use those.

See also

References
  1. PostgreSQL Wiki: SQL/MED
  2. Chapter 5.12, "Foreign Data" of the PostgreSQL Guide.
  3. LucidDB Architecture
  4. CONNECT storage engine
  5. Farrago SQL/MED Support
  6. IBM federated database technology
  7. Teiid Documentation


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.