dbix::class::storage::dbi::sqlite(3) [mojave man page]

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

NAME

       DBIx::Class::Storage::DBI::SQLite - Automatic primary key class for SQLite

SYNOPSIS

	 # In your table classes
	 use base 'DBIx::Class::Core';
	 __PACKAGE__->set_primary_key('id');

DESCRIPTION

       This class implements autoincrements for SQLite.

   Known Issues
       RT79576
	    NOTE - This section applies to you only if ALL of these are true:

	     * You are or were using DBD::SQLite with a version lesser than 1.38_01

	     * You are or were using DBIx::Class versions between 0.08191 and 0.08209
	       (inclusive) or between 0.08240-TRIAL and 0.08242-TRIAL (also inclusive)

	     * You use objects with overloaded stringification and are feeding them
	       to DBIC CRUD methods directly

	   An unfortunate chain of events led to DBIx::Class silently hitting the problem described in RT#79576
	   <https://rt.cpan.org/Public/Bug/Display.html?id=79576>.

	   In order to trigger the bug condition one needs to supply more than one bind value that is an object with overloaded stringification
	   (numification is not relevant, only stringification is). When this is the case the internal DBIx::Class call to "$sth->bind_param"
	   would be executed in a way that triggers the above-mentioned DBD::SQLite bug. As a result all the logs and tracers will contain the
	   expected values, however SQLite will receive all these bind positions being set to the value of the last supplied stringifiable object.

	   Even if you upgrade DBIx::Class (which works around the bug starting from version 0.08210) you may still have corrupted/incorrect data
	   in your database.  DBIx::Class will currently detect when this condition (more than one stringifiable object in one CRUD call) is
	   encountered and will issue a warning pointing to this section. This warning will be removed 2 years from now, around April 2015, You
	   can disable it after you've audited your data by setting the "DBIC_RT79576_NOWARN" environment variable. Note - the warning is emitted
	   only once per callsite per process and only when the condition in question is encountered. Thus it is very unlikely that your logsystem
	   will be flooded as a result of this.

METHODS

   connect_call_use_foreign_keys
       Used as:

	   on_connect_call => 'use_foreign_keys'

       In connect_info to turn on foreign key (including cascading) support for recent versions of SQLite and DBD::SQLite.

       Executes:

	 PRAGMA foreign_keys = ON

       See <http://www.sqlite.org/foreignkeys.html> for more information.

AUTHOR AND CONTRIBUTORS

       See AUTHOR and CONTRIBUTORS in DBIx::Class

LICENSE

       You may distribute this code under the same terms as Perl itself.

perl v5.18.2							    2014-01-29				      DBIx::Class::Storage::DBI::SQLite(3)

Check Out this Related Man Page

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

NAME

       DBIx::Class::Storage::DBI::SQLAnywhere - Driver for SQL Anywhere

DESCRIPTION

       This class implements autoincrements for SQL Anywhere and provides DBIx::Class::InflateColumn::DateTime support and support for the
       "uniqueidentifier" type (via DBIx::Class::Storage::DBI::SQLAnywhere::Cursor.)

       You need the "DBD::SQLAnywhere" driver that comes with the SQL Anywhere distribution, NOT the one on CPAN. It is usually under a path such
       as:

	 /opt/sqlanywhere11/sdk/perl

       Recommended connect_info settings:

	 on_connect_call => 'datetime_setup'

METHODS

   connect_call_datetime_setup
       Used as:

	   on_connect_call => 'datetime_setup'

       In connect_info to set the date and timestamp formats (as temporary options for the session) for use with
       DBIx::Class::InflateColumn::DateTime.

       The "TIMESTAMP" data type supports up to 6 digits after the decimal point for second precision. The full precision is used.

       The "DATE" data type supposedly stores hours and minutes too, according to the documentation, but I could not get that to work. It seems to
       only store the date.

       You will need the DateTime::Format::Strptime module for inflation to work.

MAXIMUM CURSORS

       A DBIx::Class application can use a lot of cursors, due to the usage of prepare_cached.

       The default cursor maximum is 50, which can be a bit too low. This limit can be turned off (or increased) by the DBA by executing:

	 set option max_statement_count = 0
	 set option max_cursor_count	= 0

       Highly recommended.

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::SQLAnywhere(3pm)

Linux and UNIX Man Pages

dbix::class::storage::dbi::sqlite(3) [mojave man page]

Check Out this Related Man Page