Content-Type: text/plain;
  charset="iso-8859-1"
From: Ian Barwick <barwick@gmx.net>
To: "jack" <datactrl@tpg.com.au>, <pgsql-sql@postgresql.org>
Subject: Re: EXECUTE problem on schema
Date: Fri, 28 Mar 2003 09:34:59 +0100
References: <000f01c2f403$c6fc7bf0$1400a8c0@jac>
	<200303271111.24745.barwick@gmx.net>
	<004501c2f4c5$5116f970$1400a8c0@jac>
In-Reply-To: <004501c2f4c5$5116f970$1400a8c0@jac>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200303280934.59317.barwick@gmx.net>

On Friday 28 March 2003 01:59, jack wrote:

(...)
>  And the following are the example.

Aha, the problem is not EXECUTE but QUOTE_IDENT:

  test=3D# SELECT quote_ident('public.test_j2');
     quote_ident=20=20=20=20
  ------------------
   "public.test_j2"
  (1 row)

  test=3D# SELECT * FROM "public.test_j2";
  ERROR:  Relation "public.test_j2" does not exist

which is correct, because schema and relation names can contain periods.
To quote a schema-qualified relation name you need something like
"public"."test_j2" (or "public"."table.with_period_in_name") which
quote_indent can't handle because it doesn't know whether the
period is a schema / relation name divider or part of the relation name.

This has come up before, see:
http://archives.postgresql.org/pgsql-hackers/2002-11/msg00892.php

It would probably be easiest to leave out the quote_ident from your
function definition and do the quoting manually in the function call,
if necessary, which mostly isn't.

Ian Barwick
barwick@gmx.net