SQLite does not currently support dropping foreign key constraints by alter statements. This means that tables cannot be dropped if there are any rows that depend on those. If there are cycles between tables, it would even be excessively difficult to delete the data in the right order first. Because of this, we just turn off the foreign constraints before we drop the schema and hope that we're not going to break anything. :( We could theoretically check for data consistency afterwards, but we don't currently.

Namespace: NHibernate.Dialect
Assembly: NHibernate (in NHibernate.dll) Version: 3.2.0.4000 (3.2.0.4000)

Syntax

C#
public override string DisableForeignKeyConstraintsString { get; }
Visual Basic
Public Overrides ReadOnly Property DisableForeignKeyConstraintsString As String
	Get
Visual C++
public:
virtual property String^ DisableForeignKeyConstraintsString {
	String^ get () override;
}

See Also