1 package DBIx::Class::Storage::DBI::SQLite;
6 use base qw/DBIx::Class::Storage::DBI/;
9 use SQL::Abstract 'is_plain_value';
10 use DBIx::Class::_Util qw(modver_gt_or_eq sigwarn_silencer);
11 use DBIx::Class::Carp;
15 __PACKAGE__->sql_maker_class('DBIx::Class::SQLMaker::SQLite');
16 __PACKAGE__->sql_limit_dialect ('LimitOffset');
17 __PACKAGE__->sql_quote_char ('"');
18 __PACKAGE__->datetime_parser_type ('DateTime::Format::SQLite');
22 DBIx::Class::Storage::DBI::SQLite - Automatic primary key class for SQLite
26 # In your table classes
27 use base 'DBIx::Class::Core';
28 __PACKAGE__->set_primary_key('id');
32 This class implements autoincrements for SQLite.
40 NOTE - This section applies to you only if ALL of these are true:
42 * You are or were using DBD::SQLite with a version lesser than 1.38_01
44 * You are or were using DBIx::Class versions between 0.08191 and 0.08209
45 (inclusive) or between 0.08240-TRIAL and 0.08242-TRIAL (also inclusive)
47 * You use objects with overloaded stringification and are feeding them
48 to DBIC CRUD methods directly
50 An unfortunate chain of events led to DBIx::Class silently hitting the problem
51 described in L<RT#79576|https://rt.cpan.org/Public/Bug/Display.html?id=79576>.
53 In order to trigger the bug condition one needs to supply B<more than one>
54 bind value that is an object with overloaded stringification (numification
55 is not relevant, only stringification is). When this is the case the internal
56 DBIx::Class call to C<< $sth->bind_param >> would be executed in a way that
57 triggers the above-mentioned DBD::SQLite bug. As a result all the logs and
58 tracers will contain the expected values, however SQLite will receive B<all>
59 these bind positions being set to the value of the B<last> supplied
62 Even if you upgrade DBIx::Class (which works around the bug starting from
63 version 0.08210) you may still have corrupted/incorrect data in your database.
64 DBIx::Class warned about this condition for several years, hoping to give
65 anyone affected sufficient notice of the potential issues. The warning was
66 removed in version 0.082900.
80 my ($self, $dir) = @_;
83 ## Where is the db file?
84 my $dsn = $self->_dbi_connect_info()->[0];
86 my $dbname = $1 if($dsn =~ /dbname=([^;]+)/);
89 $dbname = $1 if($dsn =~ /^dbi:SQLite:(.+)$/i);
91 $self->throw_exception("Cannot determine name of SQLite db file")
92 if(!$dbname || !-f $dbname);
94 # print "Found database: $dbname\n";
95 # my $dbfile = file($dbname);
96 my ($vol, $dbdir, $file) = File::Spec->splitpath($dbname);
97 # my $file = $dbfile->basename();
98 $file = POSIX::strftime("%Y-%m-%d-%H_%M_%S", localtime()) . $file;
99 $file = "B$file" while(-f $file);
101 mkdir($dir) unless -f $dir;
102 my $backupfile = File::Spec->catfile($dir, $file);
104 my $res = File::Copy::copy($dbname, $backupfile);
105 $self->throw_exception("Backup failed! ($!)") if(!$res);
110 sub _exec_svp_begin {
111 my ($self, $name) = @_;
113 $self->_dbh->do("SAVEPOINT $name");
116 sub _exec_svp_release {
117 my ($self, $name) = @_;
119 $self->_dbh->do("RELEASE SAVEPOINT $name");
122 sub _exec_svp_rollback {
123 my ($self, $name) = @_;
125 $self->_dbh->do("ROLLBACK TO SAVEPOINT $name");
127 # resync state for older DBD::SQLite (RT#67843)
128 # https://github.com/DBD-SQLite/DBD-SQLite/commit/9b3cdbf
130 ! modver_gt_or_eq('DBD::SQLite', '1.33')
132 $self->_dbh->FETCH('AutoCommit')
134 $self->_dbh->STORE('AutoCommit', 0);
135 $self->_dbh->STORE('BegunWork', 1);
142 # Be extremely careful what we do here. SQLite is notoriously bad at
143 # synchronizing its internal transaction state with {AutoCommit}
144 # https://metacpan.org/source/ADAMK/DBD-SQLite-1.37/lib/DBD/SQLite.pm#L921
145 # There is a function http://www.sqlite.org/c3ref/get_autocommit.html
146 # but DBD::SQLite does not expose it (nor does it seem to properly use it)
148 # Therefore only execute a "ping" when we have no other choice *AND*
149 # scrutinize the thrown exceptions to make sure we are where we think we are
150 my $dbh = $self->_dbh or return undef;
151 return undef unless $dbh->FETCH('Active');
152 return undef unless $dbh->ping;
156 # older DBD::SQLite does not properly synchronize commit state between
157 # the libsqlite and the $dbh
158 unless (defined $DBD::SQLite::__DBIC_TXN_SYNC_SANE__) {
159 $DBD::SQLite::__DBIC_TXN_SYNC_SANE__ = modver_gt_or_eq('DBD::SQLite', '1.38_02');
162 # fallback to travesty
163 unless ($DBD::SQLite::__DBIC_TXN_SYNC_SANE__) {
164 # since we do not have access to sqlite3_get_autocommit(), do a trick
165 # to attempt to *safely* determine what state are we *actually* in.
167 # also using T::T here leads to bizarre leaks - will figure it out later
168 my $really_not_in_txn = do {
171 # older versions of DBD::SQLite do not properly detect multiline BEGIN/COMMIT
172 # statements to adjust their {AutoCommit} state. Hence use such a statement
173 # pair here as well, in order to escape from poking {AutoCommit} needlessly
174 # https://rt.cpan.org/Public/Bug/Display.html?id=80087
176 # will fail instantly if already in a txn
177 $dbh->do("-- multiline\nBEGIN");
178 $dbh->do("-- multiline\nCOMMIT");
181 ($@ =~ /transaction within a transaction/)
188 # if we were unable to determine this - we may very well be dead
189 if (not defined $really_not_in_txn) {
192 # check the AC sync-state
193 elsif ($really_not_in_txn xor $dbh->{AutoCommit}) {
195 'Internal transaction state of handle %s (apparently %s a transaction) does not seem to '
196 . 'match its AutoCommit attribute setting of %s - this is an indication of a '
197 . 'potentially serious bug in your transaction handling logic',
199 $really_not_in_txn ? 'NOT in' : 'in',
200 $dbh->{AutoCommit} ? 'TRUE' : 'FALSE',
203 # it is too dangerous to execute anything else in this state
204 # assume everything works (safer - worst case scenario next statement throws)
209 # do the actual test and return on no failure
210 ( $ping_fail ||= ! try { $dbh->do('SELECT * FROM sqlite_master LIMIT 1'); 1 } )
211 or return 1; # the actual RV of _ping()
213 # ping failed (or so it seems) - need to do some cleanup
214 # it is possible to have a proper "connection", and have "ping" return
215 # false anyway (e.g. corrupted file). In such cases DBD::SQLite still
216 # keeps the actual file handle open. We don't really want this to happen,
217 # so force-close the handle via DBI itself
219 local $@; # so that we do not clobber the real error as set above
220 eval { $dbh->disconnect }; # if it fails - it fails
221 undef; # the actual RV of _ping()
224 sub deployment_statements {
226 my ($schema, $type, $version, $dir, $sqltargs, @rest) = @_;
231 ! exists $sqltargs->{producer_args}{sqlite_version}
233 my $dver = $self->_server_info->{normalized_dbms_version}
235 $sqltargs->{producer_args}{sqlite_version} = $dver;
238 $self->next::method($schema, $type, $version, $dir, $sqltargs, @rest);
241 sub bind_attribute_by_data_type {
243 # According to http://www.sqlite.org/datatype3.html#storageclasses
244 # all numeric types are dynamically allocated up to 8 bytes per
246 # Thus it should be safe and non-wasteful to bind everything as
247 # SQL_BIGINT and have SQLite deal with storage/comparisons however
249 $_[1] =~ /^ (?: int(?:[1248]|eger)? | (?:tiny|small|medium|big)int ) $/ix
255 # FIXME - what the flying fuck... work around RT#76395
256 # DBD::SQLite warns on binding >32 bit values with 32 bit IVs
260 DBIx::Class::_ENV_::IV_SIZE < 8
262 DBIx::Class::_ENV_::OS_NAME eq 'MSWin32'
265 ! defined $DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT
267 $DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT = (
268 modver_gt_or_eq('DBD::SQLite', '1.37')
272 local $SIG{__WARN__} = sigwarn_silencer( qr/
273 \Qdatatype mismatch: bind\E \s (?:
274 param \s+ \( \d+ \) \s+ [-+]? \d+ (?: \. 0*)? \Q as integer\E
276 \d+ \s type \s @{[ DBI::SQL_BIGINT() ]} \s as \s [-+]? \d+ (?: \. 0*)?
280 DBIx::Class::_ENV_::IV_SIZE < 8
282 DBIx::Class::_ENV_::OS_NAME eq 'MSWin32'
285 $DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT
288 shift->next::method(@_);
291 # DBD::SQLite (at least up to version 1.31 has a bug where it will
292 # non-fatally numify a string value bound as an integer, resulting
293 # in insertions of '0' into supposed-to-be-numeric fields
294 # Since this can result in severe data inconsistency, remove the
295 # bind attr if such a situation is detected
297 # FIXME - when a DBD::SQLite version is released that eventually fixes
298 # this situation (somehow) - no-op this override once a proper DBD
299 # version is detected
300 sub _dbi_attrs_for_bind {
301 my ($self, $ident, $bind) = @_;
303 my $bindattrs = $self->next::method($ident, $bind);
305 if (! defined $DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values) {
306 $DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values
307 = modver_gt_or_eq('DBD::SQLite', '1.37') ? 1 : 0;
310 for my $i (0.. $#$bindattrs) {
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 if ($bind->[$i][1] > 0x7fff_ffff or $bind->[$i][1] < -0x8000_0000) {
336 carp_unique( sprintf (
337 "An integer value occupying more than 32 bits was supplied for column '%s' "
338 . 'which your version of DBD::SQLite (%s) can not bind properly so DBIC '
339 . 'will treat it as a string instead, consider upgrading to at least '
340 . 'DBD::SQLite version 1.37',
341 $bind->[$i][0]{dbic_colname} || "# $i",
342 DBD::SQLite->VERSION,
344 undef $bindattrs->[$i];
347 $bindattrs->[$i] = DBI::SQL_INTEGER()
356 =head2 connect_call_use_foreign_keys
360 on_connect_call => 'use_foreign_keys'
362 In L<connect_info|DBIx::Class::Storage::DBI/connect_info> to turn on foreign key
363 (including cascading) support for recent versions of SQLite and L<DBD::SQLite>.
367 PRAGMA foreign_keys = ON
369 See L<http://www.sqlite.org/foreignkeys.html> for more information.
373 sub connect_call_use_foreign_keys {
377 'PRAGMA foreign_keys = ON'
381 =head1 FURTHER QUESTIONS?
383 Check the list of L<additional DBIC resources|DBIx::Class/GETTING HELP/SUPPORT>.
385 =head1 COPYRIGHT AND LICENSE
387 This module is free software L<copyright|DBIx::Class/COPYRIGHT AND LICENSE>
388 by the L<DBIx::Class (DBIC) authors|DBIx::Class/AUTHORS>. You can
389 redistribute it and/or modify it under the same terms as the
390 L<DBIx::Class library|DBIx::Class/COPYRIGHT AND LICENSE>.