Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dbix::class::storage::dbi::ado::ms_jet(3) [osx man page]

DBIx::Class::Storage::DBI::ADO::MS_Jet(3)		User Contributed Perl Documentation		 DBIx::Class::Storage::DBI::ADO::MS_Jet(3)

DBIx::Class::Storage::DBI::ADO::MS_Jet - Support for MS Access over ADO DESCRIPTION
This driver is a subclass of DBIx::Class::Storage::DBI::ADO and DBIx::Class::Storage::DBI::ACCESS for connecting to MS Access via DBD::ADO. See the documentation for DBIx::Class::Storage::DBI::ACCESS for information on the MS Access driver for DBIx::Class. This driver implements workarounds for "TEXT/IMAGE/MEMO" columns, sets the cursor_class to DBIx::Class::Storage::DBI::ADO::MS_Jet::Cursor to normalize returned "GUID" values and provides DBIx::Class::InflateColumn::DateTime support for "DATETIME" columns. EXAMPLE DSNs # older Access versions: dbi:ADO:Microsoft.Jet.OLEDB.4.0;Data Source=C:Users kitoverDocumentsaccess_sample.accdb # newer Access versions: dbi:ADO:Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:Users kitoverDocumentsaccess_sample.accdb;Persist Security Info=False' TEXT
/IMAGE/MEMO COLUMNS The ADO driver does not suffer from the problems the ODBC driver has with these types of columns. You can use them safely. When you execute a "CREATE TABLE" statement over this driver with a "TEXT" column, it will be converted to "MEMO", while in the ODBC driver it is converted to "VARCHAR(255)". However, the caveat about LongReadLen having to be twice the max size of your largest "MEMO/TEXT" column +1 still applies. DBD::ADO sets LongReadLen to a large value by default, so it should be safe to just leave it unset. If you do pass a LongReadLen in your connect_info, it will be multiplied by two and 1 added, just as for the ODBC driver. AUTHOR
See "AUTHOR" in DBIx::Class and "CONTRIBUTORS" in DBIx::Class. LICENSE
You may distribute this code under the same terms as Perl itself. perl v5.16.2 2012-08-16 DBIx::Class::Storage::DBI::ADO::MS_Jet(3)

Check Out this Related Man Page

DBIx::Class::Storage::DBI::ODBC::ACCESS(3)		User Contributed Perl Documentation		DBIx::Class::Storage::DBI::ODBC::ACCESS(3)

DBIx::Class::Storage::DBI::ODBC::ACCESS - Support specific to MS Access over ODBC DESCRIPTION
This class implements support specific to Microsoft Access over ODBC. It is a subclass of DBIx::Class::Storage::DBI::ODBC and DBIx::Class::Storage::DBI::ACCESS, see those classes for more information. It is loaded automatically by DBIx::Class::Storage::DBI::ODBC when it detects a MS Access back-end. This driver implements workarounds for "IMAGE" and "MEMO" columns, and DBIx::Class::InflateColumn::DateTime support for "DATETIME" columns. EXAMPLE DSN
dbi:ODBC:driver={Microsoft Access Driver (*.mdb, *.accdb)};dbq=C:Users kitoverDocumentsaccess_sample.accdb TEXT
/IMAGE/MEMO COLUMNS Avoid using "TEXT" columns as they will be truncated to 255 bytes. Some other drivers (like ADO) will automatically convert "TEXT" columns to "MEMO", but the ODBC driver does not. "IMAGE" columns work correctly, but the statements for inserting or updating an "IMAGE" column will not be cached, due to a bug in the Access ODBC driver. "MEMO" columns work correctly as well, but you must take care to set LongReadLen to "$max_memo_size * 2 + 1". This is done for you automatically if you pass LongReadLen in your connect_info; but if you set this attribute directly on the $dbh, keep this limitation in mind. AUTHOR
See "AUTHOR" in DBIx::Class and "CONTRIBUTORS" in DBIx::Class. LICENSE
You may distribute this code under the same terms as Perl itself. perl v5.18.2 2014-01-05 DBIx::Class::Storage::DBI::ODBC::ACCESS(3)
Man Page