77
77
>1.2. libdbi Concepts and Terminology</A
80
> In this guide, the terms <SPAN
80
>In this guide, the terms <SPAN
85
85
>"programmer"</SPAN
87
interchangably, since the target audience is the software developer using libdbi in
88
his program. The libdbi architecture provides serveral <SPAN
86
> are used interchangably, since the target audience is the software developer using libdbi in his program. A star character (*) represents a wildcard matching any letters. For example, <SPAN
89
> would represent all functions beginning with <SPAN
94
>Before doing anything useful, your program must initialize libdbi. This creates an <SPAN
97
> of libdbi which is accessible through a handle. The libdbi architecture provides several <SPAN
92
for each type of database server. All drivers are loaded into memory upon libdbi
93
initiallization and are made available to the programmer. Once a driver is
100
>, one for each type of database server. All drivers are loaded into memory by each libdbi instance upon initialization and are made available to the programmer. Once a driver is <EM
96
>, it represents a distinct database session and is
102
>, it represents a distinct database session and is called a <SPAN
99
104
>"connection"</SPAN
100
>. Multiple connections may exist for a single driver, and
101
all will function independently of each other. A star character (*) represents a
102
wildcard matching any letters. For example, <SPAN
106
represent all functions beginning with <SPAN
113
108
CLASS="NAVFOOTER"