Re: BUG #18796: Npgsql Driver: Foreign Key Read Inversion in INSERT Operations

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "rujjinjakka(at)rocketmail(dot)com" <rujjinjakka(at)rocketmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #18796: Npgsql Driver: Foreign Key Read Inversion in INSERT Operations
Date: 2025-02-06 00:06:37
Message-ID: CAKFQuwYFLLXQZZZak7oWHXxh6_jT2qNNBergdQ+dixNQs3remA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wednesday, February 5, 2025, PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 18796
> Logged by: Iza Souza
> Email address: rujjinjakka(at)rocketmail(dot)com
> PostgreSQL version: 16.0
> Operating system: Windows
> Description:
>
> I'm noticing that the key is being read in reverse order in the ORM. It's
> not matching what's happening in the table. I'm going to be forced to
> delete
> a foreign key that was created correctly, but is not being read correctly.
> The table was created by the Ngpsql driver in a C# API. It was created
> correctly - along with the foreign keys. I can insert via SQL, but the ORM
> can't insert into what it created itself, I'm on .NET 8 and I can't migrate
> to .NET 9. What can I do? Create navigation? The FK was created and is
> working... at least for Postgres;
>
>
The people who develop that driver are not part of the core PostgreSQL
community for whom this bug reporting list is intended. You will probably
want to find out where they have setup their own support community and post
this issue there.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2025-02-06 02:43:21 Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
Previous Message David Steele 2025-02-05 20:24:52 Bug in recovery of drop database?