| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Stef <stef(at)chronozon(dot)artofdns(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFC: Query Planner making a distinction between Cross |
| Date: | 2004-02-12 20:59:30 |
| Message-ID: | Pine.LNX.4.33.0402121358490.6043-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 12 Feb 2004, Stef wrote:
> > Ummmm. Postgresql doesn't natively support cross database queries...
> >
>
> I know, but it does schema's, and currently, the same
> notation is used to specify schema's as 'cross database'.
>
> So the planner often reports 'cross-database not allowed'
> in areas where it should at least report 'cross-schema
> support is unavailable for this'
>
> case in point, the example trigger. i would have expected
> deliberate schemaname.table during an insert to work, but
> instead the parser complains about cross-database.
I would think just changing the error message to "no schema by the name of
suchandsuch found" would make it pretty clear.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jo Voordeckers | 2004-02-12 21:09:03 | Re: Restore live backup from posgtres/data/base/* gives PHPPGADMIN errors, works fine otherwise |
| Previous Message | Stef | 2004-02-12 20:56:30 | Re: RFC: Query Planner making a distinction between Cross Database and Cross Schema ? |