On 9/1/06, Randall Lucas <[EMAIL PROTECTED]> wrote:
On Fri, Sep 01, 2006 at 09:30:57AM -0400, Merlin Moncure wrote: > A key tenet of relational thinking is to reduce all information to its > functional dependencies, and to try and avoid as much as possible > keeping information state in the data in a declarative sense. > last_query_shown_tuples() is imo a violation in that sense.I used last_query_shown_tuples() as a quick example. It seems more likely that it would be implemented in fact as something like EXPLAIN, where it acts upon a given query. Like, EXPLAIN DEPENDENCIES SELECT * FROM ... It seems that the query planner *must* know which rows, from which tables, actually get used in producing the output for a given query. Given that this info is present somewhere in the depths, is there a way to get this information out to the app level?
not exactly in the sense you are describing, but you can make the query such that it gives you the knowledge to get back to the original data and look it up, yes? merlin ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
