BUG #2867: FULL PATH name problem - Mailing list pgsql-bugs

From Ted Petrosky
Subject BUG #2867: FULL PATH name problem
Date
Msg-id 200612280015.kBS0FIvw064028@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #2867: FULL PATH name problem
List pgsql-bugs
The following bug has been logged online:

Bug reference:      2867
Logged by:          Ted Petrosky
Email address:      tedpet5@yahoo.com
PostgreSQL version: 8.2
Operating system:   OS X
Description:        FULL PATH name problem
Details:

I have been working with WebObjects and the EOModeler. When I tell EOModeler
to examine a table, it comes up with this for the primary key.

ALTER TABLE public.article ADD CONSTRAINT public.article_PK PRIMARY KEY
(entityid);

I must change it to be:
ALTER TABLE public.article ADD CONSTRAINT article_PK PRIMARY KEY
(entityid);
because postgresql doesn't like the 'public.' after the CONSTRAINT. I guess
the question is, should it?

Ted

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2849: Erroronous UPDATE syntax in documentation
Next
From: Tom Lane
Date:
Subject: Re: BUG #2867: FULL PATH name problem