I'd have thought that if you're using DBI with placeholders (either DBI-style ? or Oracle-style :1), the DBI should handle all your, err, quoting needs, without needing to use Oracle-specific features.
However, the Oracle and Oracle8 DBD drivers do offer some support for Oracle-specific features, such as specifying the handling of BLOBs/LOBs/CLOBs. Some of these features are done through private methods on Oracle DBI objects, called via func(). (such as $oradbh->func('plsql_errstr')), and some are done as private attributes on the DBI handler. According to the DBI specification, private (database-specific attributes) of a handler are distinguished from DBI-global ones by starting with a lower-case letter
$dbh->LongTruncOK; # all DBI handles have this $dbh->specAttribute; # not portable across databases
hth
/=\update: removed an innaccurate comment about which DBI attributes are DBD-specific, and corrected syntax for dbi private method calls.
In reply to Re: Can SQL*PLUS features be set via the DBI module ?
by ViceRaid
in thread Can SQL*PLUS features be set via the DBI module ?
by brahma
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |