Re: Problem with schemas, possibly oids?

Arni <[email protected]>
Newsgroups gmane.comp.db.postgresql.admin
Organization BIOS ICT d.o.o. Split
Message-ID <[email protected]>
On 09/08/2019 12.19, Luca Ferrari wrote:
> On Fri, Aug 9, 2019 at 12:04 PM Arni <[email protected]> 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!)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.