- FURTHER QUESTIONS?
- COPYRIGHT AND LICENSE
DBIx::Class::Storage::DBI::SQLite - Automatic primary key class for SQLite
# In your table classes use base 'DBIx::Class::Core'; __PACKAGE__->set_primary_key('id');
This class implements autoincrements for SQLite.
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 (numification is not relevant, only stringification is). When this is the case the internal DBIx::Class call to
$sth->bind_paramwould 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 warned about this condition for several years, hoping to give anyone affected sufficient notice of the potential issues. The warning was removed in 2015/v0.082820.
on_connect_call => 'use_foreign_keys'
PRAGMA foreign_keys = ON
See http://www.sqlite.org/foreignkeys.html for more information.
Check the list of additional DBIC resources.