Re: RFC: Query Planner making a distinction between Cross Database and Cross Schema ?

From: Stef <stef(at)chronozon(dot)artofdns(dot)com>
To: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: RFC: Query Planner making a distinction between Cross Database and Cross Schema ?
Date: 2004-02-12 21:28:08
Message-ID: 20040212212808.GE2137@survivor.hades
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > 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.
>

indeed, the only problem being, that this is a
-deliberately- called schema and it does exist
jst that its not in the search_path. surely the
pl/pglsql or parser should be able to search the
schemanames if i give it a -deliberate- name and
if it isnt there say 'not found' ?

so, either thats an error (improper parsing/expr
forming) in the pl/pgsql trigger code, or, well,
i dont know.

thoughts ? comments ? barking mad ?
Stef

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message ow 2004-02-12 21:49:23 Re: 7.4 - FK constraint performance
Previous Message Jo Voordeckers 2004-02-12 21:09:03 Re: Restore live backup from posgtres/data/base/* gives PHPPGADMIN errors, works fine otherwise