From b71c5a6c7d6a1e72222b4782f382e848ee6e2863 Mon Sep 17 00:00:00 2001 From: Kenichi Ishigaki Date: Mon, 11 Jan 2016 15:54:59 +0900 Subject: [PATCH] removed a big warning on foreign keys --- lib/DBD/SQLite.pm | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git a/lib/DBD/SQLite.pm b/lib/DBD/SQLite.pm index d377032..c53c0d9 100644 --- a/lib/DBD/SQLite.pm +++ b/lib/DBD/SQLite.pm @@ -1228,16 +1228,13 @@ named) placeholders to avoid confusion. =head2 Foreign Keys -B - SQLite has started supporting foreign key constraints since 3.6.19 (released on Oct 14, 2009; bundled in DBD::SQLite 1.26_05). To be exact, SQLite has long been able to parse a schema with foreign keys, but the constraints has not been enforced. Now you can issue -a pragma actually to enable this feature and enforce the constraints. - -To do this, issue the following pragma (see below), preferably as -soon as you connect to a database and you're not in a transaction: +a C pragma to enable this feature and enforce the +constraints, preferably as soon as you connect to a database and +you're not in a transaction: $dbh->do("PRAGMA foreign_keys = ON"); @@ -1251,11 +1248,9 @@ SQLite team, and by us, to secure backward compatibility, as this feature may break your applications, and actually broke some for us. If you have used a schema with foreign key constraints but haven't cared them much and supposed they're always ignored for -SQLite, be prepared, and B. It is very likely that the SQLite -team will turn it default-on in the future, and we plan to do it -NO LATER THAN they do so. +support is enabled by default. See L for details.