Skip site navigation (1) Skip section navigation (2)

Re: recent ALTER whatever .. SET SCHEMA refactoring

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: recent ALTER whatever .. SET SCHEMA refactoring
Date: 2013-01-15 14:21:05
Message-ID: 20130115142105.GC4146@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Alvaro Herrera escribió:
> Kohei KaiGai escribió:
> 
> > I'm probably saying same idea. It just adds invocation of external
> > functions to check naming conflicts of functions or collation; that
> > takes additional 4-lines for special case handling
> > in AlterObjectNamespace_internal().
> 
> Okay, I can agree with this implementation plan.

Actually, now that I look again, this is all completely broken, because
the "object already exists in schema foo" message is using
getObjectDescription infrastructure, which we agree to be completely
wrong.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


In response to

Responses

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2013-01-15 14:25:40
Subject: Re: system administration functions with hardcoded superuser checks
Previous:From: Heikki LinnakangasDate: 2013-01-15 14:05:57
Subject: Teaching pg_receivexlog to follow timeline switches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group