Re: BUG #18494: hstore data type not recognized by Npgsql in PostgreSQL 16.3

From: Pierre Forstmann <pierre(dot)forstmann(at)gmail(dot)com>
To: barankurtbogan(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18494: hstore data type not recognized by Npgsql in PostgreSQL 16.3
Date: 2024-06-04 16:09:45
Message-ID: CAM-sOH_Jzd5kCdMydoaHKX9vpijf2tb8mKBfBSjn9z71Qw9z4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

This does not look like a PostgreSQL error message but instead a Npgsql
error message (I cannot find something similar in PG 16.3 source code).

You should create an issue for Npgsql project:
https://github.com/npgsql/npgsql/issues

Le mar. 4 juin 2024 à 17:11, PG Bug reporting form <noreply(at)postgresql(dot)org>
a écrit :

> The following bug has been logged on the website:
>
> Bug reference: 18494
> Logged by: baran kurtbogan
> Email address: barankurtbogan(at)gmail(dot)com
> PostgreSQL version: 16.3
> Operating system: macOS sonoma 14.5 (23F79)
> Description:
>
> Version:
>
> PostgreSQL 16.3,
> Npgsql.EntityFrameworkCore.PostgreSQL 7.0.4 ,
> Entity Framework 7.0.8
>
> Platform: Dotnet 7
>
> I'm getting the following error when trying to work with an hstore data
> type
> in PostgreSQL 16.3, while it was working fine in PostgreSQL 16.1:
> The field 'xxx' has a type currently unknown to Npgsql (OID 17521). You can
> retrieve it as a string by marking it as unknown, please see the FAQ.
>
> Since the same operations were working in 16.1, I had to downgrade my
> version from 16.3 to 16.1 to avoid this issue.
> Data should be read and written without any issues using the hstore data
> type.
>
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-06-04 17:05:57 Re: Visibility of a local variable
Previous Message David G. Johnston 2024-06-04 16:01:56 Re: Visibility of a local variable