Sun Storage J4000 Arrays as 3000-Mailbox Solution for Microsoft Exchange 2007 With LC
This validated storage solution uses Sun Storage J4000 array family for a 3000-mailbox Microsoft Exchange 2007 implementation with Local Continuous Replication (LCR).
DBIx::Class::Storage::DBI::ODBC::ACCESS(3) User Contributed Perl Documentation DBIx::Class::Storage::DBI::ODBC::ACCESS(3)NAME
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)