agora inbox for postgres@postgres.berkeley.edu  

help / color / mirror / Atom feed

From: Paul M. Aoki <aoki@postgres.Berkeley.EDU>
To: Niranjan Perera <perera@pollux.cs.uga.edu>
Cc: postgres@postgres.Berkeley.EDU
Subject: Re: A better way ?
Date: Sun, 15 May 94 20:34:13 -0700
Message-ID: <199405160334.UAA21274@faerie.CS.Berkeley.EDU> (raw)
In-Reply-To: <9405160236.AA04523@pollux.cs.uga.edu>

Niranjan Perera <perera@pollux.cs.uga.edu> writes:
> I have a class that keeps a list of classes. What I would like to know
> is there an efficent way for me to find out if any new classes  have been
> created since I last accessed the database, by comparing against my class ?

if your actual goal is *this* part:

> is there an efficent way for me to find out if any new classes  have been
> created since I last accessed the database

then here's a gross hack to do that:

retrieve (c.relname)
from c in pg_class, a in pg_attribute
where a.tmin > "May 10 1994"::abstime	/* your last access time goes here. */
and a.attname = "oid"			/* just because oid always exists. */
and c.oid = a.attrelid
\g

aren't time-domain addressable databases fun?  if someone comes along
and modifies your oid attribute this doesn't work quite right, but if
they do that you probably have bigger problems.. (that's why i didn't
use pg_class.tmin -- pg_class tuples are modified every time you
vacuum.)

you might have to add some typecasts to make this work right with 4.1,
i don't know.

if you need "myclass" for other reasons, this probably does want you
want, too.  this is probably what you're doing already:

retrieve into difftable (pg_class.relname)
where pg_class.relname !~ "pg_"
and pg_class.relname != "myclass"
\g
delete difftable
where difftable.relname = myclass.relname
\g
retrieve (difftable.relname)
\g

it's a pain but it should be efficient enough if you index
myclass.relname.
--
  Paul M. Aoki  |  CS Div., Dept. of EECS, UCB  |  aoki@postgres.Berkeley.EDU
                |  Berkeley, CA 94720           |  ...!uunet!ucbvax!aoki

===============================================================================
    To add/remove yourself from the POSTGRES mailing list: send mail with 
    the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"

    If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
    a human will deal with it.  DO NOT post to the "postgres" mailing list.
===============================================================================

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: postgres@postgres.berkeley.edu
  Cc: aoki@postgres.Berkeley.EDU, perera@pollux.cs.uga.edu
  Subject: Re: A better way ?
  In-Reply-To: <199405160334.UAA21274@faerie.CS.Berkeley.EDU>

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

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