| From: | "Ted Petrosky" <tedpet5(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #2867: FULL PATH name problem |
| Date: | 2006-12-28 00:15:18 |
| Message-ID: | 200612280015.kBS0FIvw064028@wwwmaster.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 2867
Logged by: Ted Petrosky
Email address: tedpet5(at)yahoo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-12-28 01:17:50 | Re: BUG #2867: FULL PATH name problem |
| Previous Message | Tom Lane | 2006-12-27 16:08:45 | Re: BUG #2849: Erroronous UPDATE syntax in documentation |