1 package DBIx::Class::Storage::DBI::SQLite;
6 use base qw/DBIx::Class::Storage::DBI/;
9 use DBIx::Class::_Util qw(modver_gt_or_eq sigwarn_silencer);
10 use DBIx::Class::Carp;
14 __PACKAGE__->sql_maker_class('DBIx::Class::SQLMaker::SQLite');
15 __PACKAGE__->sql_limit_dialect ('LimitOffset');
16 __PACKAGE__->sql_quote_char ('"');
17 __PACKAGE__->datetime_parser_type ('DateTime::Format::SQLite');
21 DBIx::Class::Storage::DBI::SQLite - Automatic primary key class for SQLite
25 # In your table classes
26 use base 'DBIx::Class::Core';
27 __PACKAGE__->set_primary_key('id');
31 This class implements autoincrements for SQLite.
39 NOTE - This section applies to you only if ALL of these are true:
41 * You are or were using DBD::SQLite with a version lesser than 1.38_01
43 * You are or were using DBIx::Class versions between 0.08191 and 0.08209
44 (inclusive) or between 0.08240-TRIAL and 0.08242-TRIAL (also inclusive)
46 * You use objects with overloaded stringification and are feeding them
47 to DBIC CRUD methods directly
49 An unfortunate chain of events led to DBIx::Class silently hitting the problem
50 described in L<RT#79576|https://rt.cpan.org/Public/Bug/Display.html?id=79576>.
52 In order to trigger the bug condition one needs to supply B<more than one>
53 bind value that is an object with overloaded stringification (numification
54 is not relevant, only stringification is). When this is the case the internal
55 DBIx::Class call to C<< $sth->bind_param >> would be executed in a way that
56 triggers the above-mentioned DBD::SQLite bug. As a result all the logs and
57 tracers will contain the expected values, however SQLite will receive B<all>
58 these bind positions being set to the value of the B<last> supplied
61 Even if you upgrade DBIx::Class (which works around the bug starting from
62 version 0.08210) you may still have corrupted/incorrect data in your database.
63 DBIx::Class will currently detect when this condition (more than one
64 stringifiable object in one CRUD call) is encountered and will issue a warning
65 pointing to this section. This warning will be removed 2 years from now,
66 around April 2015, You can disable it after you've audited your data by
67 setting the C<DBIC_RT79576_NOWARN> environment variable. Note - the warning
68 is emitted only once per callsite per process and only when the condition in
69 question is encountered. Thus it is very unlikely that your logsystem will be
70 flooded as a result of this.
84 my ($self, $dir) = @_;
87 ## Where is the db file?
88 my $dsn = $self->_dbi_connect_info()->[0];
90 my $dbname = $1 if($dsn =~ /dbname=([^;]+)/);
93 $dbname = $1 if($dsn =~ /^dbi:SQLite:(.+)$/i);
95 $self->throw_exception("Cannot determine name of SQLite db file")
96 if(!$dbname || !-f $dbname);
98 # print "Found database: $dbname\n";
99 # my $dbfile = file($dbname);
100 my ($vol, $dbdir, $file) = File::Spec->splitpath($dbname);
101 # my $file = $dbfile->basename();
102 $file = POSIX::strftime("%Y-%m-%d-%H_%M_%S", localtime()) . $file;
103 $file = "B$file" while(-f $file);
105 mkdir($dir) unless -f $dir;
106 my $backupfile = File::Spec->catfile($dir, $file);
108 my $res = File::Copy::copy($dbname, $backupfile);
109 $self->throw_exception("Backup failed! ($!)") if(!$res);
114 sub _exec_svp_begin {
115 my ($self, $name) = @_;
117 $self->_dbh->do("SAVEPOINT $name");
120 sub _exec_svp_release {
121 my ($self, $name) = @_;
123 $self->_dbh->do("RELEASE SAVEPOINT $name");
126 sub _exec_svp_rollback {
127 my ($self, $name) = @_;
129 # For some reason this statement changes the value of $dbh->{AutoCommit}, so
130 # we localize it here to preserve the original value.
131 local $self->_dbh->{AutoCommit} = $self->_dbh->{AutoCommit};
133 $self->_dbh->do("ROLLBACK TRANSACTION TO SAVEPOINT $name");
139 # Be extremely careful what we do here. SQLite is notoriously bad at
140 # synchronizing its internal transaction state with {AutoCommit}
141 # https://metacpan.org/source/ADAMK/DBD-SQLite-1.37/lib/DBD/SQLite.pm#L921
142 # There is a function http://www.sqlite.org/c3ref/get_autocommit.html
143 # but DBD::SQLite does not expose it (nor does it seem to properly use it)
145 # Therefore only execute a "ping" when we have no other choice *AND*
146 # scrutinize the thrown exceptions to make sure we are where we think we are
147 my $dbh = $self->_dbh or return undef;
148 return undef unless $dbh->FETCH('Active');
149 return undef unless $dbh->ping;
153 # older DBD::SQLite does not properly synchronize commit state between
154 # the libsqlite and the $dbh
155 unless (defined $DBD::SQLite::__DBIC_TXN_SYNC_SANE__) {
156 $DBD::SQLite::__DBIC_TXN_SYNC_SANE__ = modver_gt_or_eq('DBD::SQLite', '1.38_02');
159 # fallback to travesty
160 unless ($DBD::SQLite::__DBIC_TXN_SYNC_SANE__) {
161 # since we do not have access to sqlite3_get_autocommit(), do a trick
162 # to attempt to *safely* determine what state are we *actually* in.
164 # also using T::T here leads to bizarre leaks - will figure it out later
165 my $really_not_in_txn = do {
168 # older versions of DBD::SQLite do not properly detect multiline BEGIN/COMMIT
169 # statements to adjust their {AutoCommit} state. Hence use such a statement
170 # pair here as well, in order to escape from poking {AutoCommit} needlessly
171 # https://rt.cpan.org/Public/Bug/Display.html?id=80087
173 # will fail instantly if already in a txn
174 $dbh->do("-- multiline\nBEGIN");
175 $dbh->do("-- multiline\nCOMMIT");
178 ($@ =~ /transaction within a transaction/)
185 # if we were unable to determine this - we may very well be dead
186 if (not defined $really_not_in_txn) {
189 # check the AC sync-state
190 elsif ($really_not_in_txn xor $dbh->{AutoCommit}) {
192 'Internal transaction state of handle %s (apparently %s a transaction) does not seem to '
193 . 'match its AutoCommit attribute setting of %s - this is an indication of a '
194 . 'potentially serious bug in your transaction handling logic',
196 $really_not_in_txn ? 'NOT in' : 'in',
197 $dbh->{AutoCommit} ? 'TRUE' : 'FALSE',
200 # it is too dangerous to execute anything else in this state
201 # assume everything works (safer - worst case scenario next statement throws)
206 # do the actual test and return on no failure
207 ( $ping_fail ||= ! try { $dbh->do('SELECT * FROM sqlite_master LIMIT 1'); 1 } )
208 or return 1; # the actual RV of _ping()
210 # ping failed (or so it seems) - need to do some cleanup
211 # it is possible to have a proper "connection", and have "ping" return
212 # false anyway (e.g. corrupted file). In such cases DBD::SQLite still
213 # keeps the actual file handle open. We don't really want this to happen,
214 # so force-close the handle via DBI itself
216 local $@; # so that we do not clobber the real error as set above
217 eval { $dbh->disconnect }; # if it fails - it fails
218 undef; # the actual RV of _ping()
221 sub deployment_statements {
223 my ($schema, $type, $version, $dir, $sqltargs, @rest) = @_;
228 ! exists $sqltargs->{producer_args}{sqlite_version}
230 my $dver = $self->_server_info->{normalized_dbms_version}
232 $sqltargs->{producer_args}{sqlite_version} = $dver;
235 $sqltargs->{quote_identifiers}
236 = !!$self->sql_maker->_quote_chars
237 if ! exists $sqltargs->{quote_identifiers};
239 $self->next::method($schema, $type, $version, $dir, $sqltargs, @rest);
242 sub bind_attribute_by_data_type {
244 # According to http://www.sqlite.org/datatype3.html#storageclasses
245 # all numeric types are dynamically allocated up to 8 bytes per
247 # Thus it should be safe and non-wasteful to bind everything as
248 # SQL_BIGINT and have SQLite deal with storage/comparisons however
250 $_[1] =~ /^ (?: int(?:[1248]|eger)? | (?:tiny|small|medium|big)int ) $/ix
256 # FIXME - what the flying fuck... work around RT#76395
257 # DBD::SQLite warns on binding >32 bit values with 32 bit IVs
260 DBIx::Class::_ENV_::IV_SIZE < 8
262 ! defined $DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT
264 $DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT = (
265 modver_gt_or_eq('DBD::SQLite', '1.37')
269 local $SIG{__WARN__} = sigwarn_silencer( qr/
270 \Qdatatype mismatch: bind\E \s (?:
271 param \s+ \( \d+ \) \s+ [-+]? \d+ (?: \. 0*)? \Q as integer\E
273 \d+ \s type \s @{[ DBI::SQL_BIGINT() ]} \s as \s [-+]? \d+ (?: \. 0*)?
275 /x ) if DBIx::Class::_ENV_::IV_SIZE < 8 and $DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT;
277 shift->next::method(@_);
280 # DBD::SQLite (at least up to version 1.31 has a bug where it will
281 # non-fatally numify a string value bound as an integer, resulting
282 # in insertions of '0' into supposed-to-be-numeric fields
283 # Since this can result in severe data inconsistency, remove the
284 # bind attr if such a situation is detected
286 # FIXME - when a DBD::SQLite version is released that eventually fixes
287 # this situation (somehow) - no-op this override once a proper DBD
288 # version is detected
289 sub _dbi_attrs_for_bind {
290 my ($self, $ident, $bind) = @_;
292 my $bindattrs = $self->next::method($ident, $bind);
294 # somewhere between 1.33 and 1.37 things went horribly wrong
295 if (! defined $DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values) {
296 $DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values = (
297 modver_gt_or_eq('DBD::SQLite', '1.34')
299 ! modver_gt_or_eq('DBD::SQLite', '1.37')
303 # an attempt to detect former effects of RT#79576, bug itself present between
304 # 0.08191 and 0.08209 inclusive (fixed in 0.08210 and higher)
305 my $stringifiable = 0;
307 for my $i (0.. $#$bindattrs) {
309 $stringifiable++ if ( length ref $bind->[$i][1] and overload::Method($bind->[$i][1], '""') );
312 defined $bindattrs->[$i]
314 defined $bind->[$i][1]
316 grep { $bindattrs->[$i] eq $_ } (
317 DBI::SQL_INTEGER(), DBI::SQL_TINYINT(), DBI::SQL_SMALLINT(), DBI::SQL_BIGINT()
320 if ( $bind->[$i][1] !~ /^ [\+\-]? [0-9]+ (?: \. 0* )? $/x ) {
321 carp_unique( sprintf (
322 "Non-integer value supplied for column '%s' despite the integer datatype",
323 $bind->[$i][0]{dbic_colname} || "# $i"
325 undef $bindattrs->[$i];
328 ! $DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values
330 # unsigned 32 bit ints have a range of −2,147,483,648 to 2,147,483,647
331 # alternatively expressed as the hexadecimal numbers below
332 # the comparison math will come out right regardless of ivsize, since
333 # we are operating within 31 bits
334 # P.S. 31 because one bit is lost for the sign
335 ($bind->[$i][1] > 0x7fff_ffff or $bind->[$i][1] < -0x8000_0000)
337 carp_unique( sprintf (
338 "An integer value occupying more than 32 bits was supplied for column '%s' "
339 . 'which your version of DBD::SQLite (%s) can not bind properly so DBIC '
340 . 'will treat it as a string instead, consider upgrading to at least '
341 . 'DBD::SQLite version 1.37',
342 $bind->[$i][0]{dbic_colname} || "# $i",
343 DBD::SQLite->VERSION,
345 undef $bindattrs->[$i];
351 'POSSIBLE *PAST* DATA CORRUPTION detected - see '
352 . 'DBIx::Class::Storage::DBI::SQLite/RT79576 or '
353 . 'http://v.gd/DBIC_SQLite_RT79576 for further details or set '
354 . '$ENV{DBIC_RT79576_NOWARN} to disable this warning. Trigger '
355 . 'condition encountered'
356 ) if (!$ENV{DBIC_RT79576_NOWARN} and $stringifiable > 1);
361 =head2 connect_call_use_foreign_keys
365 on_connect_call => 'use_foreign_keys'
367 In L<connect_info|DBIx::Class::Storage::DBI/connect_info> to turn on foreign key
368 (including cascading) support for recent versions of SQLite and L<DBD::SQLite>.
372 PRAGMA foreign_keys = ON
374 See L<http://www.sqlite.org/foreignkeys.html> for more information.
378 sub connect_call_use_foreign_keys {
382 'PRAGMA foreign_keys = ON'
388 =head1 AUTHOR AND CONTRIBUTORS
390 See L<AUTHOR|DBIx::Class/AUTHOR> and L<CONTRIBUTORS|DBIx::Class/CONTRIBUTORS> in DBIx::Class
394 You may distribute this code under the same terms as Perl itself.