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

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...