Re: altering a column's collation leaves an invalid foreign key

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>

To: Marcos Pegoraro <marcos@f10.com.br>

Cc: jian he <jian.universality@gmail.com>, Paul Jungwirth <pj@illuminatedcomputing.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2024-11-30T07:44:54Z

Lists: pgsql-hackers

On 29.11.24 15:25, Marcos Pegoraro wrote:
> Em ter., 19 de nov. de 2024 às 13:27, Peter Eisentraut 
> <peter@eisentraut.org <mailto:peter@eisentraut.org>> escreveu:
> 
>     3. Some documentation updates to explain some of the differences
>     between
>     NO ACTION and RESTRICT better.
> 
> 
> There is a typo on your commit "doc: Improve description of referential 
> actions"
> 
> There is also a noticeable difference between <literal>ON UPDATE NO
> +    ACTION</literal> (the default) and <literal>NO UPDATE RESTRICT</ 
> literal>.
> 
> Should be ON UPDATE RESTRICT, right ?

Fixed, thanks!

Commits

Fix error code for referential action RESTRICT
- 086c84b23d99 18.0 landed
doc: Improve description of referential actions
- 1e08905842fb 18.0 landed
Add tests for foreign keys with case-insensitive collations
- 4a2dbfc6be45 18.0 landed
Fix collation handling for foreign keys
- 9321d2fdf808 18.0 landed
Clarify a foreign key error message
- d7a2b5bd8718 18.0 landed