npgsql | Npgsql is the .NET data provider for PostgreSQL | SQL Database library

I migrate an ASP.NET Core project from 3.1 to 6.0.

I have copied old migration and pasted it to our new version

Migration on EF Core 3.1 (old)

I'm struggling to add an enum to a where condition I have on my queries.

I have the following definition for my class:

I'm trying to Deploy .Net 6 app with multiple projects to Linux Elastic Beanstalk Server from mac development machine. I'm having trouble querying the api after it has been deployed. I've done it in 2 ways - Just an EC2 instance by following this tutorial, just using command line, and through Elastic beanstalk console. So I have 2 EC2 instances. They both say they are running.

The project has one Asp.Net app (Vepo.Web) and 5 helper projects for the app layers. the "Vepo" project is just a placeholder I made because the internet told me there is a bug when you name your dll different to your solution; and the solution is "Vepo.sln".

The files created by the publish look like this:

I got the source code to deploy by cd into my asp.net core web app (Vepo.Web), then run dotnet publish -r linux-x64 --self-contained false --output build, then go to "Vepo.Web/build" in finder. Then select all files > right-click > compress (do not compress the parent folder!). That creates "archive.zip". Then upload "archive.zip" in the Elastic Beanstalk Console. And now it looks like this:

But I don't seem to be able to query the api. In Postman I'm trying:

ec2-54-xxx-xxx-95.ap-southeast-2.compute.amazonaws.com:5001/Users

but I get:

Error: connect ECONNREFUSED 54.xxx.xxx.95:5000

And navigating to it gives me:

I have created these inbound rules to allow anyone in because I'm desperately trying to get in:

Can someone help me be able to hit endpoints in my web API without getting 404/401? I will give any information required if I'm missing something.

UPDATE: I guess the app is running when I ssh into it and run this command (no idea how to access it from postman or my app, going to this in the browser does not work https://ec2-54-xxx-xxx-53.ap-southeast-2.compute.amazonaws.com:5001/fashionitems/search?searchTerm=B&currentPage=1&pageSize=10):

So I'm running into a rather odd issue here. I've got a PostgreSQL 14 server and I'm using the Npgsql Entity Framework Core provider to access it. If I have an Entity Framework Core entity that contains a date as a NodaTime Instant type (which becomes timestamp with time zone in the database) and try to project that via .InZone(timeZone).LocalDateTime, I run into 3 situations.

Actual example query would be something like this:

I'm trying to create a docker-compose script to fire a stack with a PostgreSql database and an ASP.NET Core 6 Web API. To test the scenario, I've created a new ASP.NET Core 6 Web API using the default template. I have then added NuGet package Npgsql (6.0.3), and a sample controller which just queries the DB engine version, e.g.:

I'm using ASP.NET Core 6 MVC to create an app linked to a database and I have an issue :

I scaffolded a controller and its views (create, edit...) but when I try to create an object to send to db with Entity Framework, the DateOnly typed fields won't work and put in this date for all dates I try to write : 292269055-12-03 (it seems to be the max value ?).

I need to use DateOnly type for compatibility reasons because the database has date columns (I found this information here https://www.npgsql.org/doc/types/datetime.html) and if I try to use datetime, it doesn't work.

There is my code :

View :

I have a problem when I SetCommandTimeout is like the method is not working properly.

I Use PostgreSQL as database, and for the EntityFramework Core I'm using Npgsql.EntityFrameworkCore.PostgreSQL with Version 5.0.5.1

In the code I Set Timeout for 1s like this context.Database.SetCommandTimeout(1); and I set a Stopwatch to check how much time it takes, but the ElapsedMiliseconds always return around 15000ms to 16000ms. so the SetCommandTimeout(1) is clearly not working.

I also tried using context.Database.SetCommandTimeout(TimeSpan.FromSeconds(1)); is not working either.

One more thing, I only want to Set Timeout for specific Request. So the other Request will have the default timeout.

Here's my code:

...Maybe using TFactory in AddDbContextFactory in EF Core extensions?

I've only seen AddDbContextFactory examples being used with just the TContext generic. They're always very explicit to say you have to use a using statement.

In similar situations (when I useClass in Angular or AddScoped in .NET Core), I make the variable I want to see in a constructor the first generic argument and the second generic argument what actually gets injected. You know, like:

I use Postgres and I have DB with a table that looks like that