Skip to main content

Cascade delete is not working anymore in EF with SQLite

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.

Comments

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

    ReplyDelete
    Replies
    1. 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

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP