| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: altering a column's collation leaves an invalid foreign key |
| Date: | 2024-11-15 14:46:15 |
| Message-ID: | 0005ebb3-75c2-4b0d-bf9b-d0ba7458a4cd@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14.11.24 12:35, jian he wrote:
> On Thu, Nov 14, 2024 at 4:04 PM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
>> I propose that I go ahead with committing the v7 patch (with your typo
>> fixes) and then we continue discussing these other issues afterwards in
>> a separate thread.
>>
> looks good to me.
done
> but in create_table.sgml
> <para>
> In addition, when the data in the referenced columns is changed,
> certain actions are performed on the data in this table's
> columns.
> <para/>
> I actually want to add a sentence like:
>
> If the references columns collation is indeterministic, we use
> bitwise comparison to
> check if the referenced columns data is being changed.
I think this is also part of the foreign key action behavior that is a
separate topic. We can discuss documentation improvements as part of that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2024-11-15 15:01:36 | Re: Disallow UPDATE/DELETE on table with unpublished generated column as REPLICA IDENTITY |
| Previous Message | Bertrand Drouvot | 2024-11-15 14:43:32 | Re: define pg_structiszero(addr, s, r) |