| description
| - The OpenLink Multi-Tier ODBC Driver for PostgreSQL (Enterprise Edition) comprises two parts. On the server you install a request broker
which handles incoming connections, and a database agent which makes the connection to the database itself.
On data-consuming machines (clients or application-servers), you install a generic client. This approach presents
an extra layer of abstraction, such that by installing one component on each client, you can connect to several servers,
or several different databases via the same broker. Multi-tier is ideally suited to larger installations where the network
administrator wishes to handle security rules and performance configurations centrally. The OpenLink Multi-Tier Drivers for
PostgreSQL are a Type-B class driver developed using the PostgreSQL network (wire) protocol interface.
- The OpenLink Multi-Tier ODBC Driver for PostgreSQL (Enterprise Edition) comprises two parts. On the server you install a request broker
which handles incoming connections, and a database agent which makes the connection to the database itself.
On data-consuming machines (clients or application-servers), you install a generic client. This approach presents
an extra layer of abstraction, such that by installing one component on each client, you can connect to several servers,
or several different databases via the same broker. Multi-tier is ideally suited to larger installations where the network
administrator wishes to handle security rules and performance configurations centrally. The OpenLink Multi-Tier Drivers for
PostgreSQL are a Type-B class driver developed using the PostgreSQL network (wire) protocol interface.
- The OpenLink Multi-Tier ODBC Driver for PostgreSQL (Enterprise Edition) comprises two parts. On the server you install a request broker
which handles incoming connections, and a database agent which makes the connection to the database itself.
On data-consuming machines (clients or application-servers), you install a generic client. This approach presents
an extra layer of abstraction, such that by installing one component on each client, you can connect to several servers,
or several different databases via the same broker. Multi-tier is ideally suited to larger installations where the network
administrator wishes to handle security rules and performance configurations centrally. The OpenLink Multi-Tier Drivers for
PostgreSQL are a Type-B class driver developed using the PostgreSQL network (wire) protocol interface.
- The OpenLink Multi-Tier ODBC Driver for PostgreSQL (Enterprise Edition) comprises two parts. On the server you install a request broker
which handles incoming connections, and a database agent which makes the connection to the database itself.
On data-consuming machines (clients or application-servers), you install a generic client. This approach presents
an extra layer of abstraction, such that by installing one component on each client, you can connect to several servers,
or several different databases via the same broker. Multi-tier is ideally suited to larger installations where the network
administrator wishes to handle security rules and performance configurations centrally. The OpenLink Multi-Tier Drivers for
PostgreSQL are a Type-B class driver developed using the PostgreSQL network (wire) protocol interface.
- The OpenLink Multi-Tier ODBC Driver for PostgreSQL (Enterprise Edition) comprises two parts. On the server you install a request broker
which handles incoming connections, and a database agent which makes the connection to the database itself.
On data-consuming machines (clients or application-servers), you install a generic client. This approach presents
an extra layer of abstraction, such that by installing one component on each client, you can connect to several servers,
or several different databases via the same broker. Multi-tier is ideally suited to larger installations where the network
administrator wishes to handle security rules and performance configurations centrally. The OpenLink Multi-Tier Drivers for
PostgreSQL are a Type-B class driver developed using the PostgreSQL network (wire) protocol interface.
- The OpenLink Multi-Tier ODBC Driver for PostgreSQL (Enterprise Edition) comprises two parts. On the server you install a request broker
which handles incoming connections, and a database agent which makes the connection to the database itself.
On data-consuming machines (clients or application-servers), you install a generic client. This approach presents
an extra layer of abstraction, such that by installing one component on each client, you can connect to several servers,
or several different databases via the same broker. Multi-tier is ideally suited to larger installations where the network
administrator wishes to handle security rules and performance configurations centrally. The OpenLink Multi-Tier Drivers for
PostgreSQL are a Type-B class driver developed using the PostgreSQL network (wire) protocol interface.
- The OpenLink Multi-Tier ODBC Driver for PostgreSQL (Enterprise Edition) comprises two parts. On the server you install a request broker
which handles incoming connections, and a database agent which makes the connection to the database itself.
On data-consuming machines (clients or application-servers), you install a generic client. This approach presents
an extra layer of abstraction, such that by installing one component on each client, you can connect to several servers,
or several different databases via the same broker. Multi-tier is ideally suited to larger installations where the network
administrator wishes to handle security rules and performance configurations centrally. The OpenLink Multi-Tier Drivers for
PostgreSQL are a Type-B class driver developed using the PostgreSQL network (wire) protocol interface.
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)
![[cxml]](/fct/images/cxml_doc.png)
![[csv]](/fct/images/csv_doc.png)
![[text]](/fct/images/ntriples_doc.png)
![[turtle]](/fct/images/n3turtle_doc.png)
![[ld+json]](/fct/images/jsonld_doc.png)
![[rdf+json]](/fct/images/json_doc.png)
![[rdf+xml]](/fct/images/xml_doc.png)
![[atom+xml]](/fct/images/atom_doc.png)
![[html]](/fct/images/html_doc.png)