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

Re: and it's not a bunny rabbit, either

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, David Fetter <david(at)fetter(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: and it's not a bunny rabbit, either
Date: 2011-01-01 22:21:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sat, Jan 1, 2011 at 4:28 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On lör, 2011-01-01 at 00:05 -0500, Robert Haas wrote:
>> Yeah, and I still believe that.  I'm having difficulty coming up with
>> a workable approach, though.
> I don't see anything wrong with having 20 or 30 messages of variants of
> "foo cannot be used on bar"
> without placeholders.

Well, that's OK with me.  It seems a little grotty, but manageably so.

1. Should we try to include the name of the object?  If so, how?

2. Can we have a variant with an SQL-command-fragment parameter?

%s cannot be used on views
where %s might be CLUSTER, DROP COLUMN, etc.

Robert Haas
The Enterprise PostgreSQL Company

In response to


pgsql-hackers by date

Next:From: Dimitri FontaineDate: 2011-01-01 22:30:47
Subject: Extension upgrade, patch v0: debug help needed
Previous:From: Robert HaasDate: 2011-01-01 22:17:17
Subject: Re: ALTER TABLE .. SET SCHEMA lock strength

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