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

Re: BUG #2867: FULL PATH name problem

From: Theodore Petrosky <tedpet5(at)yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2867: FULL PATH name problem
Date: 2006-12-28 13:26:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
So my problem is that the program EOModeler is forcing
the schema-qualified constraint. I will filed a bug
report with Apple.... Unfortunitily, I believe that
the product has been deprecated.... I have yet to get
eclipse with "entity modeler" working correctly to see
what it does the the name space....

Thanks for the reply


--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "Ted Petrosky" <tedpet5(at)yahoo(dot)com> writes:
> > 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. 
> public.article_PK PRIMARY KEY
> > (entityid);
> > I must change it to be:
> article_PK PRIMARY KEY
> > (entityid);
> > because postgresql doesn't like the 'public.'
> after the CONSTRAINT. I guess
> > the question is, should it?
> No, I think that'd be a bad idea.  The SQL spec does
> call for a
> schema-qualified constraint name here, but that's
> because they have a
> different model of the constraint namespace than we
> do, to wit, unique
> per schema vs. our unique per table.  Unless you
> want to buy into the
> SQL naming model, you shouldn't be trying to specify
> a schema name here.
> 			regards, tom lane

Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-12-29 03:42:55
Subject: Re: transactions getting slon in councurrent environment
Previous:From: Tigran MkrtchyanDate: 2006-12-28 12:12:22
Subject: transactions getting slon in councurrent environment

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