From: hubert depesz lubaczewski <depesz@depesz.com>
To: ammmkilo@163.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18560: Inconsistent Behavior of PostgreSQL 'LIKE' Operator
Date: Wed, 31 Jul 2024 11:46:46 +0200
Message-ID: <ZqoIBlVvEsntf9Eu@depesz.com> (raw)
In-Reply-To: <18560-c6c21c3b8d5c3f9b@postgresql.org>
References: <18560-c6c21c3b8d5c3f9b@postgresql.org>
On Wed, Jul 31, 2024 at 04:47:23AM +0000, PG Bug reporting form wrote:
> CREATE TABLE t0(c0 INT NOT NULL, c1 CHAR(1) UNIQUE);
I bet the thing is simply one more edge case that proves that one
shouldn't be using char(n) datatype:
https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_char.28n.29
Best regards,
depesz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: depesz@depesz.com, ammmkilo@163.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18560: Inconsistent Behavior of PostgreSQL 'LIKE' Operator
In-Reply-To: <ZqoIBlVvEsntf9Eu@depesz.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox