pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Erny <aerd@mx3.redestb.es>
To: pgsql-interfaces@postgresql.org
Subject: Meta info for queries
Date: Fri, 25 May 2001 22:30:25 +0200
Message-ID: <3b0ec030@news> (raw)

Hi all,

I would like to write an table and query editor for Posgresql รก la pgAccess.
But I would need some help from postgresql to make it work smarter.


Are there functions / switches to get the following information:
* Effective Tables included in the query (a query could call views or stored
procedures or whatever so I need info after Postgresql Rewrite unit has done
its job)
* Effective fields, that is source table and field for each of the output
fields. Columns calculated from functions should not specify this or make it
clear that this is not a direct output.
* Return all oids, although not explicitly specified in queries.
* The same for xmin (row versioning)

In MS-Access:
* primary keys are used to access rows in tables and queries
* There is an internal row versioning.
* Processes Joins in the ODBC layer, i.e., does only query tables and joins
the results at the client.

Thanx, Erny







Message-ID: <3b0ec030@news>
Permalink:  ../3b0ec030@news/
Also on:    postgresql.org/message-id/3b0ec030@news

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: aerd@mx3.redestb.es
  Subject: Re: Meta info for queries
  In-Reply-To: <3b0ec030@news>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox