Why the hell SQLite foreign key disable by default?!
Zzzz

Reminds me of a few weeks ago, trying to debug a crash on node which could only be caused by cascade not working, and finding this out first hand.

Odd decision.

I find it useful for testing purposes.
I way to often stumble into migrations that only drops a table without taking account for foreign keys thus the test fails when a key is referenced elsewhere...

I guess I could cover my tab by cleaning those foreign keys in the test before tearing it down though.

"for backwards compatibility"

http://www.sqlite.org/faq.html#q22

I hate to sound like a hipster, but I was using SQLite before they supported foreign key constraints at all, so I'm just glad they're even there now

@jallman112 Okay, at least I know the reason now.