Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dbix::class::storage::dbi::interbase(3pm) [debian man page]

DBIx::Class::Storage::DBI::InterBase(3pm)		User Contributed Perl Documentation		 DBIx::Class::Storage::DBI::InterBase(3pm)

NAME
DBIx::Class::Storage::DBI::InterBase - Driver for the Firebird RDBMS via DBD::InterBase DESCRIPTION
This driver is a subclass of DBIx::Class::Storage::DBI::Firebird::Common for use with DBD::InterBase, see that driver for general details. You need to use either the disable_sth_caching option or "connect_call_use_softcommit" (see "CAVEATS") for your code to function correctly with this driver. Otherwise you will likely get bizarre error messages such as "no statement executing". The alternative is to use the ODBC driver, which is more suitable for long running processes such as under Catalyst. To turn on DBIx::Class::InflateColumn::DateTime support, see "connect_call_datetime_setup". connect_call_use_softcommit Used as: on_connect_call => 'use_softcommit' In connect_info to set the DBD::InterBase "ib_softcommit" option. You need either this option or "disable_sth_caching => 1" for DBIx::Class code to function correctly (otherwise you may get "no statement executing" errors.) Or use the ODBC driver. The downside of using this option is that your process will NOT see UPDATEs, INSERTs and DELETEs from other processes for already open statements. connect_call_datetime_setup Used as: on_connect_call => 'datetime_setup' In connect_info to set the date and timestamp formats using: $dbh->{ib_time_all} = 'ISO'; See DBD::InterBase for more details. The "TIMESTAMP" data type supports up to 4 digits after the decimal point for second precision. The full precision is used. The "DATE" data type stores the date portion only, and it MUST be declared with: data_type => 'date' in your Result class. Timestamp columns can be declared with either "datetime" or "timestamp". You will need the DateTime::Format::Strptime module for inflation to work. For DBIx::Class::Storage::DBI::ODBC::Firebird, this is a noop. CAVEATS
o with "connect_call_use_softcommit", you will not be able to see changes made to data in other processes. If this is an issue, use disable_sth_caching as a workaround for the "no statement executing" errors, this of course adversely affects performance. Alternately, use 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.14.2 2011-05-10 DBIx::Class::Storage::DBI::InterBase(3pm)

Check Out this Related Man Page

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

NAME
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.18.2 2013-09-24 DBIx::Class::Storage::DBI::ADO::MS_Jet(3)
Man Page