use base qw/DBIx::Class::Storage::DBI/;
use mro 'c3';
+use DBIx::Class::Carp;
+use Scalar::Util 'looks_like_number';
+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.
+
+=head1 METHODS
+
+=cut
+
sub backup {
require File::Spec;
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) = @_;
+
+ # For some reason this statement changes the value of $dbh->{AutoCommit}, so
+ # we localize it here to preserve the original value.
+ local $self->_dbh->{AutoCommit} = $self->_dbh->{AutoCommit};
+
+ $self->_dbh->do("ROLLBACK TRANSACTION TO SAVEPOINT $name");
+}
+
sub deployment_statements {
my $self = shift;
my ($schema, $type, $version, $dir, $sqltargs, @rest) = @_;
$self->next::method($schema, $type, $version, $dir, $sqltargs, @rest);
}
-sub bind_attribute_by_data_type {
- $_[1] =~ /^ (?: int(?:eger)? | (?:tiny|small|medium|big)int ) $/ix
- ? do { require DBI; DBI::SQL_INTEGER() }
- : undef
- ;
+# In addition to checking for integer data_types, we need to check for generic
+# NUMBER data_types with a zero scale, such as NUMBER(38,0) in Oracle, which are
+# integer types. Because bind_attribute_by_data_type cannot check the
+# column_info size, and the regexes are very hairy, we do the checking in
+# _resolve_bindattrs and cache the result of the check in the column_info.
+#
+sub _resolve_bindattrs {
+ my $self = shift;
+ my ($ident, $bind, $colinfos) = @_;
+
+ $colinfos = $self->_resolve_column_info($ident)
+ unless keys %$colinfos;
+
+ my $binds = $self->next::method(@_);
+
+ BIND: foreach my $bind (@$binds) {
+ my $attrs = $bind->[0];
+ my $col = $attrs->{dbic_colname};
+
+ if (exists $colinfos->{$col}{_is_integer_data_type}
+ && $colinfos->{$col}{_is_integer_data_type} == 1) { # cached
+
+ $attrs->{dbd_attrs} = do { require DBI; DBI::SQL_INTEGER() };
+ next BIND;
+ }
+
+ my $data_type = $attrs->{sqlt_datatype};
+ my $size = $attrs->{sqlt_size};
+
+ my $is_int_type = $self->_is_integer_type($data_type) ? 1 : 0;
+
+ # This should really live in ::DBI and cache in column_info, but currently
+ # only needed in SQLite.
+ if ((not $is_int_type)
+ && (ref $size eq 'ARRAY' && $size->[1] == 0)
+ && $data_type =~ /^(?:real|float|double(?:\s+precision)?|dec(?:imal)?|numeric|number|fixed|money|currency)(?:\s+unsigned)?\z/i) {
+
+ $is_int_type = 1;
+ }
+
+ if ($is_int_type) {
+ $attrs->{dbd_attrs} = do { require DBI; DBI::SQL_INTEGER() };
+
+ $colinfos->{$col}{_is_integer_data_type} = 1; # cache
+ }
+ }
+
+ return $binds;
+}
+
+# DBD::SQLite (at least up to version 1.31 has a bug where it will
+# non-fatally nummify 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 sitation is detected
+#
+# FIXME - when a DBD::SQLite version is released that eventually fixes
+# this sutiation (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);
+
+ for (0.. $#$bindattrs) {
+ if (
+ defined $bindattrs->[$_]
+ and
+ defined $bind->[$_][1]
+ and
+ $bindattrs->[$_] eq DBI::SQL_INTEGER()
+ and
+ ! looks_like_number ($bind->[$_][1])
+ ) {
+ carp_unique( sprintf (
+ "Non-numeric value supplied for column '%s' despite the numeric datatype",
+ $bind->[$_][0]{dbic_colname} || "# $_"
+ ) );
+ undef $bindattrs->[$_];
+ }
+ }
+
+ return $bindattrs;
}
=head2 connect_call_use_foreign_keys
Executes:
- PRAGMA foreign_keys = ON
+ PRAGMA foreign_keys = ON
See L<http://www.sqlite.org/foreignkeys.html> for more information.
1;
-=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.
-
=head1 AUTHORS
Matt S. Trout <mst@shadowcatsystems.co.uk>