Matthew Phillips > DBIx-Class > DBIx::Class::Storage::DBI::SQLite

Download:
DBIx-Class-0.08249_05.tar.gz

Dependencies

Annotate this POD

Website

CPAN RT

New  13
Open  15
Stalled  12
View/Report Bugs
Source   Latest Release: DBIx-Class-0.082700_01

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.

In order to trigger the bug condition one needs to supply more than one bind value that is an object with overloaded stringification (nummification 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 emited only once per callsite per process and only when the condition in question is encountered. Thus it is very unlikey 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.

syntax highlighting: