| What drives the design of the DBI? |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| l | Goals of the DBI |
||||||||||||
| n | Be simple to use
for simple applications |
||||||||||||
| n | Have sufficient
flexibility to accommodate unusual |
||||||||||||
| functionality and
non-SQL databases |
|||||||||||||
| n | Conform to
applicable standards (ODBC etc.) |
||||||||||||
| n | Enable the
creation of database-independent Perl |
||||||||||||
| scripts without
being limited to the lowest functionality |
|||||||||||||
| n | Be free with open
source code |
||||||||||||
| l | A ‘higher-level’
interface than ODBC/JDBC |
||||||||||||
| 4 |