<div dir="ltr"><div class="gmail_default" style="font-family:"comic sans ms",sans-serif">>> <span style="font-family:Arial,Helvetica,sans-serif">Executing PRAGMA foreign_keys = ON</span></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif"><span style="font-family:Arial,Helvetica,sans-serif">This is also done for Spatialite in the SpatialiteProvider, so this is not a general GeoPackage issue.</span></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif"><span style="font-family:Arial,Helvetica,sans-serif">The need to keep this on is important, since the TRIGGERS enforces the 'sanity' of the data (such as same srid and geometry-type rules).</span></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div class="gmail_default">Also the Database-Designer can add there own rules, make a general, semi automatic  'repair' routines basically impossible.</div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif"><span style="font-family:Arial,Helvetica,sans-serif">Mark</span></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div></div>