From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
---|---|
To: | Arni <Arni(dot)Kromic(at)bios-ict(dot)hr> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Problem with schemas, possibly oids? |
Date: | 2019-08-09 10:19:50 |
Message-ID: | CAKoxK+64YQ-=0eMWMxiw+-ktcJ6sydHLK_eSX6OYNivubwbTXQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, Aug 9, 2019 at 12:04 PM Arni <Arni(dot)Kromic(at)bios-ict(dot)hr> wrote:
> Apparently, postgres thinks the identifier should be quoted if it
> contains capitals, and not if there are none (or any other characters it
> finds offensive!) That inevitably leads to different behaviors for
> different types of identifier names, which may introduce subtle bugs as
> is the case here.
And this is the behaviour I was expecting by quote_ident and
format('%I'), so I still don't see the case for the bug here. Unless
you are mixing upper and lower cases passing arguments to the
function, such as clone_schema( 'foo') and expecting it will clone
"FOO".
That's my fault, I cannot see the problem with quote_ident as it has
been applied consistently.
Luca
From | Date | Subject | |
---|---|---|---|
Next Message | Arni | 2019-08-09 10:40:54 | Re: Problem with schemas, possibly oids? |
Previous Message | Arni | 2019-08-09 10:04:46 | Re: Problem with schemas, possibly oids? |