EF6 - UTC DateTime

EF - Save datetime with specific timezone in DB but read it as UTC

Is there a mapping configuration in Entity Framework where I can state to convert any datetime that i will be saving in the db to a specific timezone (eg CEST) and whenever I read it from DB, it should be converted to UTC?

EF AsNoTracking Causes error. Expression of type 'System.DateTime' cannot be used for assignment to type 'System.Nullable`1[System.DateTime]'

Today I decided to upgrade an old web project of mine from Asp.net core 1.1 to 2.1 and all was going quite smoothly until I attempted to retrieve a list of LocalEvent's from the DB. I was using .AsNotracking as I didn't need to make any changes to the objects beyond sorting / filtering. ...This is the error:...Expression of type 'System.DateTime' c...

How do I get EntityFrameworkCore generated SQL to use the right format for DateTime objects?

I'm using ...Microsoft.EntityFrameworkCore.SqlServer v2.1.2... (and have also tried v2.2.0-preview1-35029) and am using LINQ to fetch a collection of entities from an Azure SqlServer database, filtering on a DateTime field. ...However, the SQL generated by the LINQ statement uses a string-based DateTime value that SqlServer rejects with this error...

Argument types do not match, DateTime and DateTime

Exception Argument types do not match is thrown, although both of them are DateTime. Exception is thrown at ...CreatedAt = db.TransactionLogs .Last(x => x.TransactionId == a.Id) .CreatedAt ...Query works just fine if I put CreatedAt = DateTime.Now() instead...TransactionLogs.CreatedAt is not nullable an...

DateTime.Now default value in entity configuration always sets the same DateTime in the database

I'm having a strange issue when configuring my entities in Fluent API using EF Core....All my entities have an ...EntityCreated... field which is a DateTime object that is set to the current DateTime upon being added to the database as a new record....The following is my configuration code to set this default value:...builder.Property(x => x.Entity...

Npgsql, error during saving a DateTime value (null value in column "CreatedAt" violates not-null constraint)

I have the following model: ...public class Product { public int Id { get; set; } public string Name { get; set; } public string Description { get; set; } public string Category { get; set; } public decimal Price { get; set; } [DatabaseGenerated(DatabaseGeneratedOption.Computed)] [ScaffoldColumn(false)] public D...

Asp.Net Core Convert UTC (YYYY-MM-DDThh:mm:ss.sTZD) input to LocalDateTime

I an working with an MVC .Net Core API that injests a DateTime value as YYYY-MM-DDThh:mm:ss.sTZD. However when it posts the data to the SQL database it comes out as YYYY-MM-DDThh:mm:ss.s. (example of issue below)...Input... 2020-01-21T17:05:30.3416751-05:00 ...What Gets Written to the Database...2020-01-21 22:05:30.343...Given that the input format...

.NET Core Entity Framework Fluent api error, DateTime properties have text as column type

In my model namespace, I have different model classes. I have ...DateTime... fields in my different classes. When I run ...dotnet ef migrations add InitialCreate ...without problem, it adds a migration and I am able to update the database too....When I looked up my ...initialCommit.Designer.cs..., I saw that all of my ...DateTime... properties hav...

DateTime property causing new migration update even without any update on model in Entity Framework core

In entity framework, if I run the command "...add-migration <name>..." in package manager console, each and every time it creates migration with some update commands for the property datetime....Model:...public class TestDetailBase { public string TestTitle { get; set; } public int TotalTimeinMinutes { get; set; } public...

Is there any sense to store a UTC date in DateTimeOffset Column instead of DateTime(2)?

For me it should be Localtime stored DateTimeOffset OR UTC in DateTime(2). Not UTC in DateTimeOffset. But I might be wrong....Is there any logical reason to store UTC in a DateTimeOffSet DB.Column? If so, it will always look like " +00:00" Makes no sense. Does a DateTimeOffset Column consume more than 8 bytes?