From: Joop <root@localhost.localdomain.invalid>
Subject: stored queries
Date: Tue, 23 Dec 2003 10:25:42 +0100
Organization: Hub.Org Networking Services
Lines: 25
Message-ID: <pan.2003.12.23.09.23.24.185553@localhost.localdomain.invalid>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing
	moment of clarity.)
To: pgsql-sql@postgresql.org

Hello everyone,

I'm just about to start on the reporting part of a PostgreSQL / PHP
application. I think it would be a good idea to create a table in my db in
which I can store queries, something like this:

create table stored_queries (
  id bigint primary key,
  name varchar,
  description varchar,
  parameters varchar[][],
  query text
);

The frontend to it would present the user with a choice of the NAMEs of
the records, check if PARAMETERs are required (the dimensions would be
name and datatype), if so ask for the parameters and eventually run QUERY
with these parameters.

This approach seems very logical to me, so I think someone must have
invented this weel already :-). I googled for "stored queries" but didn't
find much. I would really like tips, feedback on this approach. Is it a
bad idea, and if so, why? What pitfalls will I run into?

Thanks!