simcop2387/DBD-SQLite-SQLcipher
1
0
Fork 0
mirror of https://github.com/DBD-SQLite/DBD-SQLite synced 2025-06-07 14:19:10 -04:00
Code Issues Releases Wiki Activity

add sqlite_defensive option

Browse source
This commit is contained in:
Kenichi Ishigaki 2018-12-22 15:18:41 +09:00
parent 30c290f49f
commit a719c681d4
3 changed files with 27 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
dbdimp.c
View file

@ -459,6 +459,15 @@ sqlite_db_login6(SV *dbh, imp_dbh_t *imp_dbh, char *dbname, char *user, char *pa
sqlite3_busy_timeout(imp_dbh->db, SQL_TIMEOUT); sqlite3_busy_timeout(imp_dbh->db, SQL_TIMEOUT);
if (hv) {
if (hv_exists(hv, "sqlite_defensive", 16)) {
val = hv_fetch(hv, "sqlite_defensive", 16, 0);
if (val && SvIOK(*val)) {
sqlite3_db_config(imp_dbh->db, SQLITE_DBCONFIG_DEFENSIVE, SvIV(*val), 0);
}
}
}
#if 0 #if 0
/* /*
** As of 1.26_06 foreign keys support was enabled by default, ** As of 1.26_06 foreign keys support was enabled by default,

5
lib/DBD/SQLite.pm
View file

@ -1660,6 +1660,11 @@ for details.
If set to true, DBD::SQLite uses extended result codes where appropriate If set to true, DBD::SQLite uses extended result codes where appropriate
(see L<https://www.sqlite.org/rescode.html>). (see L<https://www.sqlite.org/rescode.html>).
=item sqlite_defensive
If set to true, language features that allow ordinary SQL to deliberately
corrupt the database file are prohibited.
=back =back
=head2 Statement Handle Attributes =head2 Statement Handle Attributes

15
t/65_db_config.t
View file

@ -11,7 +11,7 @@ use SQLiteTest qw/connect_ok @CALL_FUNCS/;
use Test::More; use Test::More;
use DBD::SQLite::Constants qw/:database_connection_configuration_options/; use DBD::SQLite::Constants qw/:database_connection_configuration_options/;
#plan tests => 7 * @CALL_FUNCS; plan tests => 38 * @CALL_FUNCS + 3;
# LOOKASIDE # LOOKASIDE
for my $func (@CALL_FUNCS) { for my $func (@CALL_FUNCS) {
@ -182,4 +182,15 @@ for my $func (@CALL_FUNCS) {
} }
} }
done_testing; # DEFENSIVE at connection
SKIP: {
skip 'DEFENSIVE is not supported', 8 if !SQLITE_DBCONFIG_DEFENSIVE;
my $dbh = connect_ok(RaiseError => 1, PrintError => 0, sqlite_defensive => 1);
my $sql = 'CREATE TABLE foo (id, text)';
$dbh->do($sql);
$dbh->do('PRAGMA writable_schema=ON');
eval { $dbh->do('UPDATE sqlite_master SET name = ? WHERE name = ?', undef, 'bar', 'foo'); };
ok $@, "updating sqlite_master is prohibited";
like $@ => qr/table sqlite_master may not be modified/;
}