[dbsrgits/DBIx-Class.git] / lib / DBIx / Class / Storage / DBI / SQLite.pm

package DBIx::Class::Storage::DBI::SQLite;

use strict;
use warnings;

use base qw/DBIx::Class::Storage::DBI/;
use mro 'c3';

use SQL::Abstract 'is_plain_value';
use DBIx::Class::_Util qw(modver_gt_or_eq sigwarn_silencer);
use DBIx::Class::Carp;
use Try::Tiny;
use namespace::clean;

__PACKAGE__->sql_maker_class('DBIx::Class::SQLMaker::SQLite');
__PACKAGE__->sql_limit_dialect ('LimitOffset');
__PACKAGE__->sql_quote_char ('"');
__PACKAGE__->datetime_parser_type ('DateTime::Format::SQLite');

=head1 NAME

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

=head1 SYNOPSIS

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

=head1 DESCRIPTION

This class implements autoincrements for SQLite.

=head2 Known Issues

=over

=item 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 L<RT#79576|https://rt.cpan.org/Public/Bug/Display.html?id=79576>.

In order to trigger the bug condition one needs to supply B<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 C<< $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 B<all>
these bind positions being set to the value of the B<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 version 0.082900.

=back

=head1 METHODS

=cut

sub backup {

  require File::Spec;
  require File::Copy;
  require POSIX;

  my ($self, $dir) = @_;
  $dir ||= './';

  ## Where is the db file?
  my $dsn = $self->_dbi_connect_info()->[0];

  my $dbname = $1 if($dsn =~ /dbname=([^;]+)/);
  if(!$dbname)
  {
    $dbname = $1 if($dsn =~ /^dbi:SQLite:(.+)$/i);
  }
  $self->throw_exception("Cannot determine name of SQLite db file")
    if(!$dbname || !-f $dbname);

#  print "Found database: $dbname\n";
#  my $dbfile = file($dbname);
  my ($vol, $dbdir, $file) = File::Spec->splitpath($dbname);
#  my $file = $dbfile->basename();
  $file = POSIX::strftime("%Y-%m-%d-%H_%M_%S", localtime()) . $file;
  $file = "B$file" while(-f $file);

  mkdir($dir) unless -f $dir;
  my $backupfile = File::Spec->catfile($dir, $file);

  my $res = File::Copy::copy($dbname, $backupfile);
  $self->throw_exception("Backup failed! ($!)") if(!$res);

  return $backupfile;
}

sub _exec_svp_begin {
  my ($self, $name) = @_;

  $self->_dbh->do("SAVEPOINT $name");
}

sub _exec_svp_release {
  my ($self, $name) = @_;

  $self->_dbh->do("RELEASE SAVEPOINT $name");
}

sub _exec_svp_rollback {
  my ($self, $name) = @_;

  $self->_dbh->do("ROLLBACK TO SAVEPOINT $name");
}

# older SQLite has issues here too - both of these are in fact
# completely benign warnings (or at least so say the tests)
sub _exec_txn_rollback {
  local $SIG{__WARN__} = sigwarn_silencer( qr/rollback ineffective/ )
    unless $DBD::SQLite::__DBIC_TXN_SYNC_SANE__;

  shift->next::method(@_);
}

sub _exec_txn_commit {
  local $SIG{__WARN__} = sigwarn_silencer( qr/commit ineffective/ )
    unless $DBD::SQLite::__DBIC_TXN_SYNC_SANE__;

  shift->next::method(@_);
}

sub _ping {
  my $self = shift;

  # Be extremely careful what we do here. SQLite is notoriously bad at
  # synchronizing its internal transaction state with {AutoCommit}
  # https://metacpan.org/source/ADAMK/DBD-SQLite-1.37/lib/DBD/SQLite.pm#L921
  # There is a function http://www.sqlite.org/c3ref/get_autocommit.html
  # but DBD::SQLite does not expose it (nor does it seem to properly use it)

  # Therefore only execute a "ping" when we have no other choice *AND*
  # scrutinize the thrown exceptions to make sure we are where we think we are
  my $dbh = $self->_dbh or return undef;
  return undef unless $dbh->FETCH('Active');
  return undef unless $dbh->ping;

  my $ping_fail;

  # older DBD::SQLite does not properly synchronize commit state between
  # the libsqlite and the $dbh
  unless (defined $DBD::SQLite::__DBIC_TXN_SYNC_SANE__) {
    $DBD::SQLite::__DBIC_TXN_SYNC_SANE__ = modver_gt_or_eq('DBD::SQLite', '1.38_02');
  }

  # fallback to travesty
  unless ($DBD::SQLite::__DBIC_TXN_SYNC_SANE__) {
    # since we do not have access to sqlite3_get_autocommit(), do a trick
    # to attempt to *safely* determine what state are we *actually* in.
    # FIXME
    # also using T::T here leads to bizarre leaks - will figure it out later
    my $really_not_in_txn = do {
      local $@;

      # older versions of DBD::SQLite do not properly detect multiline BEGIN/COMMIT
      # statements to adjust their {AutoCommit} state. Hence use such a statement
      # pair here as well, in order to escape from poking {AutoCommit} needlessly
      # https://rt.cpan.org/Public/Bug/Display.html?id=80087
      eval {
        # will fail instantly if already in a txn
        $dbh->do("-- multiline\nBEGIN");
        $dbh->do("-- multiline\nCOMMIT");
        1;
      } or do {
        ($@ =~ /transaction within a transaction/)
          ? 0
          : undef
        ;
      };
    };

    # if we were unable to determine this - we may very well be dead
    if (not defined $really_not_in_txn) {
      $ping_fail = 1;
    }
    # check the AC sync-state
    elsif ($really_not_in_txn xor $dbh->{AutoCommit}) {
      carp_unique (sprintf
        'Internal transaction state of handle %s (apparently %s a transaction) does not seem to '
      . 'match its AutoCommit attribute setting of %s - this is an indication of a '
      . 'potentially serious bug in your transaction handling logic',
        $dbh,
        $really_not_in_txn ? 'NOT in' : 'in',
        $dbh->{AutoCommit} ? 'TRUE' : 'FALSE',
      );

      # it is too dangerous to execute anything else in this state
      # assume everything works (safer - worst case scenario next statement throws)
      return 1;
    }
  }

  # do the actual test and return on no failure
  ( $ping_fail ||= ! try { $dbh->do('SELECT * FROM sqlite_master LIMIT 1'); 1 } )
    or return 1; # the actual RV of _ping()

  # ping failed (or so it seems) - need to do some cleanup
  # it is possible to have a proper "connection", and have "ping" return
  # false anyway (e.g. corrupted file). In such cases DBD::SQLite still
  # keeps the actual file handle open. We don't really want this to happen,
  # so force-close the handle via DBI itself
  #
  local $@; # so that we do not clobber the real error as set above
  eval { $dbh->disconnect }; # if it fails - it fails
  undef; # the actual RV of _ping()
}

sub deployment_statements {
  my $self = shift;
  my ($schema, $type, $version, $dir, $sqltargs, @rest) = @_;

  $sqltargs ||= {};

  if (
    ! exists $sqltargs->{producer_args}{sqlite_version}
      and
    my $dver = $self->_server_info->{normalized_dbms_version}
  ) {
    $sqltargs->{producer_args}{sqlite_version} = $dver;
  }

  $self->next::method($schema, $type, $version, $dir, $sqltargs, @rest);
}

sub bind_attribute_by_data_type {

  # According to http://www.sqlite.org/datatype3.html#storageclasses
  # all numeric types are dynamically allocated up to 8 bytes per
  # individual value
  # Thus it should be safe and non-wasteful to bind everything as
  # SQL_BIGINT and have SQLite deal with storage/comparisons however
  # it deems correct
  $_[1] =~ /^ (?: int(?:[1248]|eger)? | (?:tiny|small|medium|big)int ) $/ix
    ? DBI::SQL_BIGINT()
    : undef
  ;
}

# FIXME - what the flying fuck... work around RT#76395
# DBD::SQLite warns on binding >32 bit values with 32 bit IVs
sub _dbh_execute {
  if (
    (
      DBIx::Class::_ENV_::IV_SIZE < 8
        or
      DBIx::Class::_ENV_::OS_NAME eq 'MSWin32'
    )
      and
    ! defined $DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT
  ) {
    $DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT = (
      modver_gt_or_eq('DBD::SQLite', '1.37')
    ) ? 1 : 0;
  }

  local $SIG{__WARN__} = sigwarn_silencer( qr/
    \Qdatatype mismatch: bind\E \s (?:
      param \s+ \( \d+ \) \s+ [-+]? \d+ (?: \. 0*)? \Q as integer\E
        |
      \d+ \s type \s @{[ DBI::SQL_BIGINT() ]} \s as \s [-+]? \d+ (?: \. 0*)?
    )
  /x ) if (
    (
      DBIx::Class::_ENV_::IV_SIZE < 8
        or
      DBIx::Class::_ENV_::OS_NAME eq 'MSWin32'
    )
      and
    $DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT
  );

  shift->next::method(@_);
}

# DBD::SQLite (at least up to version 1.31 has a bug where it will
# non-fatally numify a string value bound as an integer, resulting
# in insertions of '0' into supposed-to-be-numeric fields
# Since this can result in severe data inconsistency, remove the
# bind attr if such a situation is detected
#
# FIXME - when a DBD::SQLite version is released that eventually fixes
# this situation (somehow) - no-op this override once a proper DBD
# version is detected
sub _dbi_attrs_for_bind {
  my ($self, $ident, $bind) = @_;

  my $bindattrs = $self->next::method($ident, $bind);

  if (! defined $DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values) {
    $DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values
      = modver_gt_or_eq('DBD::SQLite', '1.37') ? 1 : 0;
  }

  for my $i (0.. $#$bindattrs) {
    if (
      defined $bindattrs->[$i]
        and
      defined $bind->[$i][1]
        and
      grep { $bindattrs->[$i] eq $_ } (
        DBI::SQL_INTEGER(), DBI::SQL_TINYINT(), DBI::SQL_SMALLINT(), DBI::SQL_BIGINT()
      )
    ) {
      if ( $bind->[$i][1] !~ /^ [\+\-]? [0-9]+ (?: \. 0* )? $/x ) {
        carp_unique( sprintf (
          "Non-integer value supplied for column '%s' despite the integer datatype",
          $bind->[$i][0]{dbic_colname} || "# $i"
        ) );
        undef $bindattrs->[$i];
      }
      elsif (
        ! $DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values
      ) {
        # unsigned 32 bit ints have a range of −2,147,483,648 to 2,147,483,647
        # alternatively expressed as the hexadecimal numbers below
        # the comparison math will come out right regardless of ivsize, since
        # we are operating within 31 bits
        # P.S. 31 because one bit is lost for the sign
        if ($bind->[$i][1] > 0x7fff_ffff or $bind->[$i][1] < -0x8000_0000) {
          carp_unique( sprintf (
            "An integer value occupying more than 32 bits was supplied for column '%s' "
          . 'which your version of DBD::SQLite (%s) can not bind properly so DBIC '
          . 'will treat it as a string instead, consider upgrading to at least '
          . 'DBD::SQLite version 1.37',
            $bind->[$i][0]{dbic_colname} || "# $i",
            DBD::SQLite->VERSION,
          ) );
          undef $bindattrs->[$i];
        }
        else {
          $bindattrs->[$i] = DBI::SQL_INTEGER()
        }
      }
    }
  }

  return $bindattrs;
}

=head2 connect_call_use_foreign_keys

Used as:

    on_connect_call => 'use_foreign_keys'

In L<connect_info|DBIx::Class::Storage::DBI/connect_info> to turn on foreign key
(including cascading) support for recent versions of SQLite and L<DBD::SQLite>.

Executes:

  PRAGMA foreign_keys = ON

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

=cut

sub connect_call_use_foreign_keys {
  my $self = shift;

  $self->_do_query(
    'PRAGMA foreign_keys = ON'
  );
}

=head1 FURTHER QUESTIONS?

Check the list of L<additional DBIC resources|DBIx::Class/GETTING HELP/SUPPORT>.

=head1 COPYRIGHT AND LICENSE

This module is free software L<copyright|DBIx::Class/COPYRIGHT AND LICENSE>
by the L<DBIx::Class (DBIC) authors|DBIx::Class/AUTHORS>. You can
redistribute it and/or modify it under the same terms as the
L<DBIx::Class library|DBIx::Class/COPYRIGHT AND LICENSE>.

=cut

1;
Commit	Line	Data
843f8ecd	1	package DBIx::Class::Storage::DBI::SQLite;
	2
	3	use strict;
	4	use warnings;
2ad62d97	5
	6	use base qw/DBIx::Class::Storage::DBI/;
	7	use mro 'c3';
	8
b5ce6748	9	use SQL::Abstract 'is_plain_value';
b5ce6748	10	use DBIx::Class::_Util qw(modver_gt_or_eq sigwarn_silencer);
632d1e0f	11	use DBIx::Class::Carp;
8d1fb3e2	12	use Try::Tiny;
632d1e0f	13	use namespace::clean;
632d1e0f	14
d5dedbd6	15	__PACKAGE__->sql_maker_class('DBIx::Class::SQLMaker::SQLite');
6a247f33	16	__PACKAGE__->sql_limit_dialect ('LimitOffset');
2b8cc2f2	17	__PACKAGE__->sql_quote_char ('"');
6f7a118e	18	__PACKAGE__->datetime_parser_type ('DateTime::Format::SQLite');
09cedb88	19
2fa97c7d	20	=head1 NAME
	21
	22	DBIx::Class::Storage::DBI::SQLite - Automatic primary key class for SQLite
	23
	24	=head1 SYNOPSIS
	25
	26	# In your table classes
	27	use base 'DBIx::Class::Core';
	28	__PACKAGE__->set_primary_key('id');
	29
	30	=head1 DESCRIPTION
	31
	32	This class implements autoincrements for SQLite.
	33
75a1d824	34	=head2 Known Issues
	35
	36	=over
	37
	38	=item RT79576
	39
	40	NOTE - This section applies to you only if ALL of these are true:
	41
	42	* You are or were using DBD::SQLite with a version lesser than 1.38_01
	43
	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)
	46
	47	* You use objects with overloaded stringification and are feeding them
	48	to DBIC CRUD methods directly
	49
	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>.
	52
	53	In order to trigger the bug condition one needs to supply B<more than one>
4a0eed52	54	bind value that is an object with overloaded stringification (numification
75a1d824	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
	60	stringifiable object.
	61
	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.
cff17b97	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.
75a1d824	67
	68	=back
	69
2fa97c7d	70	=head1 METHODS
	71
	72	=cut
	73
357eb92c	74	sub backup {
	75
	76	require File::Spec;
	77	require File::Copy;
	78	require POSIX;
	79
8795fefb	80	my ($self, $dir) = @_;
8795fefb	81	$dir \|\|= './';
c9d2e0a2	82
c9d2e0a2	83	## Where is the db file?
12c9beea	84	my $dsn = $self->_dbi_connect_info()->[0];
c9d2e0a2	85
	86	my $dbname = $1 if($dsn =~ /dbname=([^;]+)/);
	87	if(!$dbname)
	88	{
	89	$dbname = $1 if($dsn =~ /^dbi:SQLite:(.+)$/i);
	90	}
357eb92c	91	$self->throw_exception("Cannot determine name of SQLite db file")
c9d2e0a2	92	if(!$dbname \|\| !-f $dbname);
	93
	94	# print "Found database: $dbname\n";
79923569	95	# my $dbfile = file($dbname);
8795fefb	96	my ($vol, $dbdir, $file) = File::Spec->splitpath($dbname);
79923569	97	# my $file = $dbfile->basename();
357eb92c	98	$file = POSIX::strftime("%Y-%m-%d-%H_%M_%S", localtime()) . $file;
c9d2e0a2	99	$file = "B$file" while(-f $file);
8795fefb	100
	101	mkdir($dir) unless -f $dir;
	102	my $backupfile = File::Spec->catfile($dir, $file);
	103
357eb92c	104	my $res = File::Copy::copy($dbname, $backupfile);
c9d2e0a2	105	$self->throw_exception("Backup failed! ($!)") if(!$res);
c9d2e0a2	106
8795fefb	107	return $backupfile;
c9d2e0a2	108	}
c9d2e0a2	109
86a51471	110	sub _exec_svp_begin {
	111	my ($self, $name) = @_;
	112
	113	$self->_dbh->do("SAVEPOINT $name");
	114	}
	115
	116	sub _exec_svp_release {
	117	my ($self, $name) = @_;
	118
	119	$self->_dbh->do("RELEASE SAVEPOINT $name");
	120	}
	121
	122	sub _exec_svp_rollback {
	123	my ($self, $name) = @_;
	124
398215b1	125	$self->_dbh->do("ROLLBACK TO SAVEPOINT $name");
	126	}
	127
	128	# older SQLite has issues here too - both of these are in fact
	129	# completely benign warnings (or at least so say the tests)
	130	sub _exec_txn_rollback {
	131	local $SIG{__WARN__} = sigwarn_silencer( qr/rollback ineffective/ )
	132	unless $DBD::SQLite::__DBIC_TXN_SYNC_SANE__;
	133
	134	shift->next::method(@_);
	135	}
	136
	137	sub _exec_txn_commit {
	138	local $SIG{__WARN__} = sigwarn_silencer( qr/commit ineffective/ )
	139	unless $DBD::SQLite::__DBIC_TXN_SYNC_SANE__;
86a51471	140
398215b1	141	shift->next::method(@_);
86a51471	142	}
86a51471	143
8d1fb3e2	144	sub _ping {
8d1fb3e2	145	my $self = shift;
2aeb3c7f	146
	147	# Be extremely careful what we do here. SQLite is notoriously bad at
	148	# synchronizing its internal transaction state with {AutoCommit}
	149	# https://metacpan.org/source/ADAMK/DBD-SQLite-1.37/lib/DBD/SQLite.pm#L921
	150	# There is a function http://www.sqlite.org/c3ref/get_autocommit.html
	151	# but DBD::SQLite does not expose it (nor does it seem to properly use it)
	152
	153	# Therefore only execute a "ping" when we have no other choice AND
	154	# scrutinize the thrown exceptions to make sure we are where we think we are
	155	my $dbh = $self->_dbh or return undef;
	156	return undef unless $dbh->FETCH('Active');
	157	return undef unless $dbh->ping;
	158
ab0b0a09	159	my $ping_fail;
	160
	161	# older DBD::SQLite does not properly synchronize commit state between
	162	# the libsqlite and the $dbh
	163	unless (defined $DBD::SQLite::__DBIC_TXN_SYNC_SANE__) {
b1dbf716	164	$DBD::SQLite::__DBIC_TXN_SYNC_SANE__ = modver_gt_or_eq('DBD::SQLite', '1.38_02');
ab0b0a09	165	}
2aeb3c7f	166
ab0b0a09	167	# fallback to travesty
	168	unless ($DBD::SQLite::__DBIC_TXN_SYNC_SANE__) {
	169	# since we do not have access to sqlite3_get_autocommit(), do a trick
	170	# to attempt to safely determine what state are we actually in.
	171	# FIXME
	172	# also using T::T here leads to bizarre leaks - will figure it out later
	173	my $really_not_in_txn = do {
	174	local $@;
	175
	176	# older versions of DBD::SQLite do not properly detect multiline BEGIN/COMMIT
	177	# statements to adjust their {AutoCommit} state. Hence use such a statement
	178	# pair here as well, in order to escape from poking {AutoCommit} needlessly
	179	# https://rt.cpan.org/Public/Bug/Display.html?id=80087
	180	eval {
	181	# will fail instantly if already in a txn
	182	$dbh->do("-- multiline\nBEGIN");
	183	$dbh->do("-- multiline\nCOMMIT");
	184	1;
	185	} or do {
	186	($@ =~ /transaction within a transaction/)
	187	? 0
	188	: undef
	189	;
	190	};
2aeb3c7f	191	};
2aeb3c7f	192
ab0b0a09	193	# if we were unable to determine this - we may very well be dead
	194	if (not defined $really_not_in_txn) {
	195	$ping_fail = 1;
	196	}
	197	# check the AC sync-state
	198	elsif ($really_not_in_txn xor $dbh->{AutoCommit}) {
	199	carp_unique (sprintf
	200	'Internal transaction state of handle %s (apparently %s a transaction) does not seem to '
	201	. 'match its AutoCommit attribute setting of %s - this is an indication of a '
	202	. 'potentially serious bug in your transaction handling logic',
	203	$dbh,
	204	$really_not_in_txn ? 'NOT in' : 'in',
	205	$dbh->{AutoCommit} ? 'TRUE' : 'FALSE',
	206	);
	207
	208	# it is too dangerous to execute anything else in this state
	209	# assume everything works (safer - worst case scenario next statement throws)
	210	return 1;
	211	}
2aeb3c7f	212	}
2aeb3c7f	213
ab0b0a09	214	# do the actual test and return on no failure
	215	( $ping_fail \|\|= ! try { $dbh->do('SELECT * FROM sqlite_master LIMIT 1'); 1 } )
	216	or return 1; # the actual RV of _ping()
	217
	218	# ping failed (or so it seems) - need to do some cleanup
	219	# it is possible to have a proper "connection", and have "ping" return
	220	# false anyway (e.g. corrupted file). In such cases DBD::SQLite still
	221	# keeps the actual file handle open. We don't really want this to happen,
	222	# so force-close the handle via DBI itself
	223	#
4a0eed52	224	local $@; # so that we do not clobber the real error as set above
ab0b0a09	225	eval { $dbh->disconnect }; # if it fails - it fails
ab0b0a09	226	undef; # the actual RV of _ping()
8d1fb3e2	227	}
8d1fb3e2	228
2361982d	229	sub deployment_statements {
96736321	230	my $self = shift;
2361982d	231	my ($schema, $type, $version, $dir, $sqltargs, @rest) = @_;
	232
	233	$sqltargs \|\|= {};
	234
96736321	235	if (
	236	! exists $sqltargs->{producer_args}{sqlite_version}
	237	and
	238	my $dver = $self->_server_info->{normalized_dbms_version}
	239	) {
	240	$sqltargs->{producer_args}{sqlite_version} = $dver;
6d766626	241	}
2361982d	242
	243	$self->next::method($schema, $type, $version, $dir, $sqltargs, @rest);
	244	}
	245
0e773352	246	sub bind_attribute_by_data_type {
04ab4eb1	247
	248	# According to http://www.sqlite.org/datatype3.html#storageclasses
	249	# all numeric types are dynamically allocated up to 8 bytes per
	250	# individual value
	251	# Thus it should be safe and non-wasteful to bind everything as
	252	# SQL_BIGINT and have SQLite deal with storage/comparisons however
	253	# it deems correct
	254	$_[1] =~ /^ (?: int(?:[1248]\|eger)? \| (?:tiny\|small\|medium\|big)int ) $/ix
	255	? DBI::SQL_BIGINT()
0e773352	256	: undef
	257	;
	258	}
	259
04ab4eb1	260	# FIXME - what the flying fuck... work around RT#76395
	261	# DBD::SQLite warns on binding >32 bit values with 32 bit IVs
	262	sub _dbh_execute {
1363f0f5	263	if (
00882d2c	264	(
	265	DBIx::Class::_ENV_::IV_SIZE < 8
	266	or
	267	DBIx::Class::_ENV_::OS_NAME eq 'MSWin32'
	268	)
1363f0f5	269	and
	270	! defined $DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT
	271	) {
	272	$DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT = (
	273	modver_gt_or_eq('DBD::SQLite', '1.37')
	274	) ? 1 : 0;
04ab4eb1	275	}
04ab4eb1	276
1363f0f5	277	local $SIG{__WARN__} = sigwarn_silencer( qr/
	278	\Qdatatype mismatch: bind\E \s (?:
	279	param \s+ \( \d+ \) \s+ [-+]? \d+ (?: \. 0*)? \Q as integer\E
	280	\|
	281	\d+ \s type \s @{[ DBI::SQL_BIGINT() ]} \s as \s [-+]? \d+ (?: \. 0*)?
	282	)
00882d2c	283	/x ) if (
	284	(
	285	DBIx::Class::_ENV_::IV_SIZE < 8
	286	or
	287	DBIx::Class::_ENV_::OS_NAME eq 'MSWin32'
	288	)
	289	and
	290	$DBD::SQLite::__DBIC_CHECK_dbd_mishandles_bound_BIGINT
	291	);
1363f0f5	292
04ab4eb1	293	shift->next::method(@_);
	294	}
	295
632d1e0f	296	# DBD::SQLite (at least up to version 1.31 has a bug where it will
4a0eed52	297	# non-fatally numify a string value bound as an integer, resulting
632d1e0f	298	# in insertions of '0' into supposed-to-be-numeric fields
632d1e0f	299	# Since this can result in severe data inconsistency, remove the
4a0eed52	300	# bind attr if such a situation is detected
632d1e0f	301	#
632d1e0f	302	# FIXME - when a DBD::SQLite version is released that eventually fixes
4a0eed52	303	# this situation (somehow) - no-op this override once a proper DBD
632d1e0f	304	# version is detected
	305	sub _dbi_attrs_for_bind {
	306	my ($self, $ident, $bind) = @_;
75a1d824	307
632d1e0f	308	my $bindattrs = $self->next::method($ident, $bind);
632d1e0f	309
04ab4eb1	310	if (! defined $DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values) {
215102b9	311	$DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values
215102b9	312	= modver_gt_or_eq('DBD::SQLite', '1.37') ? 1 : 0;
04ab4eb1	313	}
04ab4eb1	314
49f7b6c7	315	for my $i (0.. $#$bindattrs) {
632d1e0f	316	if (
49f7b6c7	317	defined $bindattrs->[$i]
632d1e0f	318	and
49f7b6c7	319	defined $bind->[$i][1]
632d1e0f	320	and
d830d9f4	321	grep { $bindattrs->[$i] eq $_ } (
	322	DBI::SQL_INTEGER(), DBI::SQL_TINYINT(), DBI::SQL_SMALLINT(), DBI::SQL_BIGINT()
	323	)
632d1e0f	324	) {
04ab4eb1	325	if ( $bind->[$i][1] !~ /^ [\+\-]? [0-9]+ (?: \. 0* )? $/x ) {
	326	carp_unique( sprintf (
	327	"Non-integer value supplied for column '%s' despite the integer datatype",
	328	$bind->[$i][0]{dbic_colname} \|\| "# $i"
	329	) );
	330	undef $bindattrs->[$i];
	331	}
	332	elsif (
	333	! $DBD::SQLite::__DBIC_CHECK_dbd_can_bind_bigint_values
215102b9	334	) {
04ab4eb1	335	# unsigned 32 bit ints have a range of −2,147,483,648 to 2,147,483,647
	336	# alternatively expressed as the hexadecimal numbers below
	337	# the comparison math will come out right regardless of ivsize, since
	338	# we are operating within 31 bits
	339	# P.S. 31 because one bit is lost for the sign
215102b9	340	if ($bind->[$i][1] > 0x7fff_ffff or $bind->[$i][1] < -0x8000_0000) {
	341	carp_unique( sprintf (
	342	"An integer value occupying more than 32 bits was supplied for column '%s' "
	343	. 'which your version of DBD::SQLite (%s) can not bind properly so DBIC '
	344	. 'will treat it as a string instead, consider upgrading to at least '
	345	. 'DBD::SQLite version 1.37',
	346	$bind->[$i][0]{dbic_colname} \|\| "# $i",
	347	DBD::SQLite->VERSION,
	348	) );
	349	undef $bindattrs->[$i];
	350	}
	351	else {
	352	$bindattrs->[$i] = DBI::SQL_INTEGER()
	353	}
04ab4eb1	354	}
632d1e0f	355	}
	356	}
	357
	358	return $bindattrs;
	359	}
	360
732e4282	361	=head2 connect_call_use_foreign_keys
	362
	363	Used as:
	364
	365	on_connect_call => 'use_foreign_keys'
	366
8384a713	367	In L<connect_info\|DBIx::Class::Storage::DBI/connect_info> to turn on foreign key
8384a713	368	(including cascading) support for recent versions of SQLite and L<DBD::SQLite>.
732e4282	369
	370	Executes:
	371
8273e845	372	PRAGMA foreign_keys = ON
732e4282	373
	374	See L<http://www.sqlite.org/foreignkeys.html> for more information.
	375
	376	=cut
	377
	378	sub connect_call_use_foreign_keys {
	379	my $self = shift;
	380
	381	$self->_do_query(
	382	'PRAGMA foreign_keys = ON'
	383	);
	384	}
	385
a2bd3796	386	=head1 FURTHER QUESTIONS?
843f8ecd	387
a2bd3796	388	Check the list of L<additional DBIC resources\|DBIx::Class/GETTING HELP/SUPPORT>.
843f8ecd	389
a2bd3796	390	=head1 COPYRIGHT AND LICENSE
843f8ecd	391
a2bd3796	392	This module is free software L<copyright\|DBIx::Class/COPYRIGHT AND LICENSE>
	393	by the L<DBIx::Class (DBIC) authors\|DBIx::Class/AUTHORS>. You can
	394	redistribute it and/or modify it under the same terms as the
	395	L<DBIx::Class library\|DBIx::Class/COPYRIGHT AND LICENSE>.
843f8ecd	396
843f8ecd	397	=cut
a2bd3796	398
a2bd3796	399	1;