Relational | A fluent, intuitive ORM for any relational database engine | Database library

I have a C# project (.NET6) that looks like this:

project.csproj

I am trying to use the new DateOnly aspects of c# but when I come to do my migrations I am having the following issue. I am using SQL Server 2019 the error is.

'Amenitie.StartDate could not be mapped because it is of type 'DateOnly', which is not a supported primitive type or a valid entity type. Either explicitly map this property, or ignore it using the'

My model is as follows

I am creating a workout app using MySQL and Prisma, and I am struggling to design a schema for the data.

The app will have users and workout programs. For example a workout program 'Get Jacked', could consist of 3 blocks (each block is 1 month). Each block will contain 5 workouts per week, each workout will contain multiple exercises and a warm up. Some important things to note: each User should be able to record their personal sets and reps for each exercise within a workout. They should also be able to complete a program ('Get Jacked'), as many times as they like and each time they should be able to record new values for their reps and sets.

Here's my models so far:

We're belatedly upgrading a successful .net Core 2.1 MVC application to .net Core 5, and everything has gone well, apart from some confusing Microsoft.Data.SqlClient.SqlException 'Execution Timeout Expired' exceptions in a number of queries that used to work perfectly well in EF Core 2.1.

This is an example of one of the queries we're having problems with

For unscoped enumerations, the answer is "most of them" because of the implicit conversions to the underlying integral type. However, scoped enumerations do not have this implicit conversion. Instead, some but not all of the operators available for unscoped enumerations are defined for them.

I have a data set of the form

that I would like to change to this form below in R using SQL.

I know that I could do this daily simply with dplyr but the point here is to learn to use SQL to create and manipulate a small relational database.

• Price needs to be turned into a numeric value. Removing the "R" and spaces in between.

• coordinates needs to be turned into 2 coordinates Long and Lat

• floor size needs to be turned into a numeric from a string removing the space and "m^2" at the end.

Minimum working example

We are running a .NET Core 3.1 application in a Kubernetes cluster. The application connects to an Azure SQL Database using EF Core 3.1.7, with Microsoft.Data.SqlClient 1.1.3.

At seemingly random times, we would receive the following error.

I added an entity class to my EF Core 5.0/MS SQL Server data model that is backed by a defining query (raw SQL query, with no table or view corresponding to it in my database).

When I make changes to it (for example, adding a new column) and then run Add-Migration in Package Manager Console to create a migration step, it generates a migration with empty Up(MigrationBuilder migrationBuilder) and Down(MigrationBuilder migrationBuilder) methods. But the generated [MigrationName].Designer.cs file contains the new column, and the ModelSnapshot for my DbContext gets modified to include the new columns, so something has changed.

My question is, do I need to add a migration each time I make a change to one of these entities in order for my app to function properly? If they're not needed, what is considered better practice when I update the defining query -backed entity:

A. Adding these migrations even though they have blank Up(MigrationBuilder migrationBuilder) and Down(MigrationBuilder migrationBuilder) methods, because the model changed, or

B. Not generating the migration and just having these changes get picked up the next time someone makes a change that actually impacts the underlying database structures?

Code snippets (over-simplified to remove identifying data):

Entity class

Here's a simple example of what I'm trying to do: