Re: Problem with schemas, possibly oids?

From: Arni <Arni(dot)Kromic(at)Bios-ICT(dot)hr>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Problem with schemas, possibly oids?
Date: 2019-08-09 10:40:54
Message-ID: 21585e7a-844c-96ae-f94b-000c712aa492@Bios-ICT.hr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 09/08/2019 12.19, Luca Ferrari wrote:
> 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.
Obviously there is a problem if it works _only_ with schemas without
capitals!
You said before:
> the first query is performed with quote_ident and that's the initial
> failure.
So I did according to whay _you_ said - removed that quote_ident - and
now it works (thanks!)

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Anjul Tyagi 2019-08-09 11:45:13 Barman With Replication server
Previous Message Luca Ferrari 2019-08-09 10:19:50 Re: Problem with schemas, possibly oids?