Skip to main content

Cascade delete is not working anymore in EF with SQLite

By
Two in one. In today post we will talk about two different topics:

  1. An example from real life that shows why unit tests are important
  2. An odd behavior of SQLite combined with Entity Framework 
Why Unit Tests are important
This days we had to update an application with the latest and greatest version of Entity Framework and SQLite. After a few hours of working we manage to update SQLite and EF to the new version and we manage to make the application to compile and start.
Now was the moment of true, to check if the unit tests are still green. And surprise, some of them are red, even if the application seems to run without any kind of problem. It seems that in the new version of EF or SQLite the behavior or functionality of a specific feature was changed.

Odd behavior of SQLite and Entity Framework
Before the update:
PRAGMA foreign_keys = ON;
DELETE FROM CarsHistory 
    WHERE (julianday(datetime('now'))-julianday(CarBuyDate))>360
Executed as a SQL command from Entity Framework used to trigger also the delete cascade in the tables around CarsHistory. This was the expected behavior, taking into account that delete cascade feature was activated for that tables.
With the latest version of EF (6.1) in combination with SQLite NuGet Package (1.0.94) we had a big surprise. The cascade deletion was not triggered anymore by the above command. We were lucky with unit tests that cached this problem immediately after update.
The final solution was pretty “special”. Move the PRAGMA command from the command query to the connection string.
Connection string:
data source=C:\Dbs\myCardDb.db;foreign keys=true;
Command:
DELETE FROM CarsHistory 
   WHERE (julianday(datetime('now'))-julianday(CarBuyDate))>360
It seems that the old method to trigger a cascade delete is not anymore supported.


In conclusion we learn that unit tests can be useful to catch odd behavior, even the one related to frameworks updates. Also, it seems that from time to time the behavior of canonical commands can change.
Labels:

Comments

  1. Cipbn3January 29, 2015 at 9:38 PM

    How we can integrate SQLite with EF into a .Net Application?

    ReplyDelete
    Replies
    1. Radu VunvuleaJanuary 30, 2015 at 12:06 AM

      I think that this link would be useful for you http://bricelam.net/2012/10/entity-framework-on-sqlite.html

      Delete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more