Re: Confusing terminology

From: Mike Mascari <mascarm(at)mascari(dot)com>
To: "Roderick A(dot) Anderson" <raanders(at)tincan(dot)org>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Confusing terminology
Date: 2002-01-19 18:44:14
Message-ID: 3C49BE7E.56EB90CF@mascari.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Roderick A. Anderson" wrote:
>
> On Fri, 18 Jan 2002, Arguile wrote:
>
> > Roderick A. Anderson writes:
>
> > > > ERROR: Relation 'foo' already exists
> > >
> > > Can a table named foo and a view named foo exist in the same database?
> > >
> > No. There's no reasonable way for the server to know which you mean when you
> > execute a statement. This applies to tables, views, sequences, etc.
>
> It was a rhetorical question (aka. smart-ass). My point was a table,
> view, sequence, and their friends are all relations. Or at least to my
> understanding the table and view are relations.
> And therefore Relation 'foo' already exists makes sense to me.

CREATE INDEX i_foo1 on foo(key);

ERROR: DefineIndex: relation "foo" not found

ALTER TABLE foo ADD COLUMN key integer;

ERROR: ALTER TABLE: column name "key" already exists in table "foo"

TRUNCATE TABLE foo;

ERROR: Relation 'foo' does not exist

Mike Mascari
mascarm(at)mascari(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Clift 2002-01-20 05:46:59 PostgreSQL 8.0 and cross-platform capabilities
Previous Message Arguile 2002-01-19 18:03:13 Re: Confusing terminology