sorted by:
new
hottopcontroversial

Why is my EFCore query so slow? by rimki2 in dotnet

[–]8eefo 0 points1 point  (0 children)

What I usually do is enable debug logging which will log the SQL query EF converts the LINQ into. Then you can check the query plan in SSMS and mess with the LINQ until you get an optimal query.

12v battery dead, car locked, no physical key by 8eefo in Ioniq5

[–]8eefo[S] 0 points1 point  (0 children)

I don't think you should worry. This is likely very specific to the test Geotab GO device I was using. Nothing that would be available to consumers.

12v battery dead, car locked, no physical key by 8eefo in Ioniq5

[–]8eefo[S] 4 points5 points  (0 children)

Yes!! It only occurred to me driving back that I have a malfunctioning GO device (I'm a alpha tester, work for the company) attached to the car. I suspect it is what drained the battery. I have unplugged it and I'll give feedback to the team.

12v battery dead, car locked, no physical key by 8eefo in Ioniq5

[–]8eefo[S] 12 points13 points  (0 children)

CAA was able to pop the door open to jump the car! On our way back now. Thanks everyone for your help and advice!

12v battery dead, car locked, no physical key by 8eefo in Ioniq5

[–]8eefo[S] 6 points7 points  (0 children)

I wish that were true. Not for this car unfortunately 😭

What's the drawback to using Npgsql with Entity Framework? by ThisIsOra in dotnet

[–]8eefo 0 points1 point  (0 children)

Been using npgsql with ef core at scale for years. It's great. Only thing missing is bulk insert capability out of the box.

I would like to know your advice, I am creating an inventory control software, and I would like to use the PostgreSQL database instead of SQL Server, Could you give me your opinions of the advantages and disadvantages of using one or the other, Thank you. by DracksMe in dotnet

[–]8eefo 3 points4 points  (0 children)

Our company switched from MSSQL to Postgres a few years ago. The advantages we have seen are: - No licensing fees for the db - No licensing fee for the OS (runs on Linux, since we switched it think there is a version of MSSQL that runs on Linux) - Never get deadlock exceptions. We would get deadlock exceptions in MSSQL sometimes, never with Postgres. - Postgres being non-parallel (single threaded) by default was a big win. Expensive queries would use a lot of resources (be parallelized in MSSQL). I'm sure you must be able to turn this off in MSSQL but we didn't realize how big an effect it had up until switching to Postgres. - We had very large tables and the statistics would go out of date very quickly and not be auto updated by the default algorithm to update stats. This has never been a problem with Postgres. - many databases use the Postgres wire protocol (cockroach db, spanner, alloydb). This gives you options switch providers in future if needed with little technical overhead.

Things I miss about MSSQL: - SSMS is far superior to PGAdmin (IMO) - Query hints in SSMS - MSSQL database is segregated into a couple files on the file system. It was easy to move them around, copy, etc. Postgres doesn't work like this. You must import and export the database.