.\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
.\" ========================================================================
.de Sh \" Subsection heading
.de Sp \" Vertical space (when we can't use .PP)
.de Vb \" Begin verbatim text
.de Ve \" End verbatim text
.\" Set up some character translations and predefined strings. \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote. | will give a
.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
. tm Index:\\$1\t\\n%\t"\\$2"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. \" simple accents for nroff and troff
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
. \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
. \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
. \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
.\" ========================================================================
.TH DBD::ADO 3 "2002-10-01" "perl v5.8.0" "User Contributed Perl Documentation"
DBD::ADO \- A DBI driver for Microsoft ADO (Active Data Objects)
\& $dbh = DBI->connect("dbi:ADO:dsn", $user, $passwd);
\& Options in the connect string:
\& dbi:ADO:dsn;CommandTimeout=60 (your number)
\& dbi:ADO:dsn;ConnectTimeout=60 (your number)
\& or include both ConnectTimeout and CommandTimeout.
\& The dsn may be a standard ODBC dsn or a dsn-less.
\& See the ADO documentation for more information on
\& the dsn-less connection.
\& # See the DBI module documentation for full details
The \s-1DBD::ADO\s0 module supports \s-1ADO\s0 access on a Win32 machine.
\&\s-1DBD::ADO\s0 is written to support the standard \s-1DBI\s0 interface to
\& $dbh = DBI->connect("dbi:ADO:dsn", $user, $passwd, $attribs);
\& Connection supports dsn and dsn-less calls.
\& $dbh = DBI->connect( "dbi:ADO:File Name=oracle.udl",
\& $user, $passwd, {RaiseError => [0|1], PrintError => [0|1],
\& AutoCommit => [0|1]});
\& In addition the following attributes may be set in the connect string:
\& WARNING: The application is responsible for passing the correct
\& information when setting any of these attributes.
.IX Header "Functions support"
\& Using the standard DBI function call
\& $dbh->func( arguments, 'function name')
\& You may access the following functions: (case sensitave)
\& All functions return a valid statement handle upon success.
\& OpenSchema supports the following arguments:
\& Any valid ADO Schema name such as
\& my $sth = $dbh->func( 'adSchemaProviderTypes', 'OpenSchema' );
.SH "Enhanced DBI Methods"
.IX Header "Enhanced DBI Methods"
.IX Subsection "table_info"
\&\fBWarning:\fR This method is experimental and may change or disappear.
\& $sth = $dbh->table_info(\e%attr);
\& $sth = $dbh->table_info({
\& Filter => q{TABLE_NAME LIKE 'C%'},
Returns an active statement handle that can be used to fetch
information about tables and views that exist in the database.
By default the handle contains the columns described in the \s-1DBI\s0 documentation:
\& TABLE_CAT, TABLE_SCHEM, TABLE_NAME, TABLE_TYPE, REMARKS
Additional ADO-only fields will be included if the ADO_Columns attribute
\& %attr = (ADO_Columns => 1);
Some \s-1ADO\s0 providers include path info in the \s-1TABLE_CAT\s0 column.
This information will be trimmed if the Trim_Catalog attribute is set to true:
\& %attr = (Trim_Catalog => 1);
The \s-1ADO\s0 driver allows column criteria to be specified. In this way the
record set can be restricted, for example, to only include tables of type '\s-1VIEW\s0':
\& %attr = (TABLE_TYPE => 'VIEW')
You can add criteria for any of the following columns:
\& TABLE_CAT, TABLE_SCHEM, TABLE_NAME, TABLE_TYPE
The \s-1ADO\s0 driver also allows the recordset to be filtered on a Criteria string:
a string made up of one or more individual clauses concatenated with \s-1AND\s0 or \s-1OR\s0 operators.
\& %attr = (Filter => q{TABLE_TYPE LIKE 'SYSTEM%'})
The criteria string is made up of clauses in the form FieldName\-Operator\-Value.
This is more flexible than using column criteria in that the filter allows a number of operators:
\& <, >, <=, >=, <>, =, or LIKE
The Fieldname must be one of the \s-1ADO\s0 '\s-1TABLES\s0 Rowset' column names:
\& TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, TABLE_TYPE, DESCRIPTION,
\& TABLE_GUID, TABLE_PROPID, DATE_CREATED, DATE_MODIFIED
Value is the value with which you will compare the field values
(for example, 'Smith', #8/24/95#, 12.345, or \f(CW$50\fR.00).
Use single quotes with strings and pound signs (#) with dates.
For numbers, you can use decimal points, dollar signs, and scientific notation.
If Operator is \s-1LIKE\s0, Value can use wildcards.
Only the asterisk (*) and percent sign (%) wild cards are allowed,
and they must be the last character in the string. Value cannot be null.
\&\fBWarning:\fR This method is experimental and may change or disappear.
\& @names = $dbh->tables(\e%attr);
Returns a list of table and view names.
Accepts any of the attributes described in the table_info method:
\& @names = $dbh->tables({ TABLE_TYPE => 'VIEW' });
\& Support for type_info_all is supported, however, you're not using
\& a true OLE DB provider (using the MS OLE DB -> ODBC), the first
\& hash may not be the "best" solution for the data type.
\& adSchemaProviderTypes does provide for a "best match" column, however
\& the MS OLE DB -> ODBC provider does not support the best match.
\& Currently the types are sorted by DATA_TYPE BEST_MATCH IS_LONG ...
It is strongly recommended that you use the latest version of \s-1ADO\s0
(2.1 at the time this was written). You can download it from:
\& http://www.microsoft.com/Data/download.htm
Phlip and Tim Bunce. With many thanks to Jan Dubois, Jochen Wiedmann
and Thomas Lowery for additions, debuggery and general help.
\&\s-1ADO\s0 Reference book: \s-1ADO\s0 2.0 Programmer's Reference, David Sussman and
Alex Homer, Wrox, \s-1ISBN\s0 1\-861001\-83\-5. If there's anything better please
http://www.able\-consulting.com/tech.htm