| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Petr Hybler <petr(dot)hybler(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PGSQL bug - "Column ??? is an identity column defined as GENERATED ALWAYS.", |
| Date: | 2021-08-19 04:51:01 |
| Message-ID: | CAKFQuwZEkGkz97e9_Pcwes=UkTh3=2oz4dnkSnMgVv+171K1hw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Aug 18, 2021 at 9:18 PM Petr Hybler <petr(dot)hybler(at)gmail(dot)com> wrote:
> Is there a possibility to have that fixed rather than using the workaround?
>
If you can prove the regression (in what v11 patch release - i.e., before
13 - did your code work, show your work please) we'd be at least willing to
consider something that could be back-patched to restore the old behavior
(which shouldn't have changed in a minor release anyway). But at the
moment we haven't observed this (I personally haven't tested though, the
bug reporter is expected to help out here).
The problem is with ORM frameworks where there is no possibility to use
> this clause OVERRIDING SYSTEM VALUE ...
>
As there is an ORM involved, the claim of this being a regression in
PostgreSQL is indeed worthy of doubt, as it may be the ORM that is at fault
here.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Semanchuk | 2021-08-19 12:43:05 | Re: PGSQL bug - "Column ??? is an identity column defined as GENERATED ALWAYS.", |
| Previous Message | Petr Hybler | 2021-08-19 04:17:54 | Re: PGSQL bug - "Column ??? is an identity column defined as GENERATED ALWAYS.", |