Foreign key constraints are not active by default.

[phongnt270]

see #450
From Official Doc :

2. Enabling Foreign Key Support
   Assuming the library is compiled with foreign key constraints enabled, it must still be enabled by the application at runtime, using the PRAGMA foreign_keys command. For example:

   sqlite> PRAGMA foreign_keys = ON;

Foreign key constraints are disabled by default (for backwards compatibility), so must be enabled separately for each database connection.

[sj26]

Ooh, nice find!

I think we can turn this on when creating the database because it's an in-memory database and we only ever have one connection.

It looks like this PR is coming from your master branch which has a merge commit as well so I'll cherry-pick the original commit and adjust directly to master.

Thanks!

[Bertg]

@sj26 Can we have a beta-3 release?

I think the lack of this PR in the beta is causing a serious bug.

Steps to reproduce:

• Send a single email to Mailcatcher
• Open said email
• Clear the emails
• Send a single email to Mailcatcher
• Open said email
• The HTML body is that of the previous email

Expected result:

See the HTML body of the new email

[cuong-nd]

@sj26 Is there any plan for release for fixing this bug, really appreciate

[sj26]

v0.8.0.beta3 is pushed!

[sj26]

This is shipped in the latest version, v0.8.0.

gem install mailcatcher

[rmacklin]

@sj26 The version constraint for sqlite3 in mailcatcher v0.8.0 is too loose due to the new requirement of SQLite3::Database responding to the foreign_keys= method, as necessitated by c887904#diff-ba6f65d5c04d1ccc77ea172c1d1769c73d099580585d07dff7496e4401298e35R39

I've opened an issue for this in #476 and a corresponding PR in #477. If it looks good to you, let me know what you think about shipping it in a new v0.8.1 release. Thanks!