dido:public:ra:xapend:xapend.b_stds:defact:microsoft:odbc
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:microsoft:odbc [2021/04/18 19:51] nick created |
dido:public:ra:xapend:xapend.b_stds:defact:microsoft:odbc [2021/09/30 14:10] (current) nick |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[dido:public:ra:xapend:xapend.b_stds:defact| return to the de Facto Standards ]] | [[dido:public:ra:xapend:xapend.b_stds:defact| return to the de Facto Standards ]] | ||
| - | : **Note:** The following is an excerpt from the official TTTTT site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. | + | : **Note:** The following is an excerpt from the official Microsoft Open [[dido:public:ra:xapend:xapend.a_glossary:d:database]] Connectivity site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. |
| Line 19: | Line 19: | ||
| ==== Introduction ==== | ==== Introduction ==== | ||
| - | // Open Database Connectivity (ODBC) is a widely accepted application programming interface (API) for database access. It is based on the Call-Level Interface (CLI) specifications from Open Group and ISO/IEC for database APIs and uses Structured Query Language (SQL) as its database access language.// | + | // [[dido:public:ra:xapend:xapend.a_glossary:o:odbc]] is a widely accepted [[dido:public:ra:xapend:xapend.a_glossary:a:api]] for database access. It is based on the Call-Level Interface (CLI) specifications from Open Group and ISO/IEC for database APIs and uses [[dido:public:ra:xapend:xapend.a_glossary:s:sql]] as its database access language.// |
| - | + | ||
| - | //ODBC is designed for maximum interoperability - that is, the ability of a single application to access different database management systems (DBMSs) with the same source code. Database applications call functions in the ODBC interface, which are implemented in database-specific modules called drivers. The use of drivers isolates applications from database-specific calls in the same way that printer drivers isolate word processing programs from printer-specific commands. Because drivers are loaded at run time, a user only has to add a new driver to access a new DBMS; it is not necessary to recompile or relink the application.// | + | |
| + | //ODBC is designed for maximum [[dido:public:ra:xapend:xapend.a_glossary:i:interoperability|interoperability ]]- that is, the ability of a single [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] to access different database management systems (DBMSs) with the same [[dido:public:ra:xapend:xapend.a_glossary:s:sourcecode|source code]]. Database applications call functions in the ODBC interface, which are implemented in database-specific modules called drivers. The use of drivers isolates applications from database-specific calls in the same way that printer drivers isolate word processing programs from printer-specific commands. Because drivers are loaded at run time, a user only has to add a new driver to access a new DBMS; it is not necessary to recompile or relink the application.// | ||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
dido/public/ra/xapend/xapend.b_stds/defact/microsoft/odbc.1618789876.txt.gz · Last modified: 2021/04/18 19:51 by nick
