That is entirely possible (;

I'm not sure if that is the way to do it or not.  My SQL is not the
greatest.

"But Schindler is bueno! Senior Burns is El Diablo!"

--------------------------------------------------------------
Website     - http://www.retrobbs.org
Tradewars - telnet tradewars.retrobbs.org
BBS          - http://bbs.retrobbs.org:8000
IRC           - irc.retrobbs.org #main
WIKI        - http://www.tpoh.org/cgi-bin/tpoh-wiki

----- Original Message ----- 
From: "Ara.T.Howard" <ahoward / noaa.gov>
Newsgroups: comp.lang.ruby
To: "ruby-talk ML" <ruby-talk / ruby-lang.org>
Sent: Wednesday, July 21, 2004 1:32 PM
Subject: Re: ruby postgresql question


> On Wed, 21 Jul 2004, Mark Firestone wrote:
>
> > Does anyone know of a good way to basically seek through a large query
> > record by record (like we used to do with the SEEK command in Clipper?)
...
> > I am converting the Ruby BBS to use postgres.  Basically, I have real
> > message numbers and the message numbers displayed by the system (so the
> > messages can be 1-x) but the real message numbers (which are unique and
> > assending) can be used to keep track of the last read pointer.
> >
> > I could make an array of message numbers, each time a user trys to pull
a
> > message up, but this seens wasteful.
> >
> > Thanks.
> >
> > Mark
>
> are you asking about cursors?
>
> -a
> --
>
============================================================================
===
> | EMAIL   :: Ara [dot] T [dot] Howard [at] noaa [dot] gov
> | PHONE   :: 303.497.6469
> | A flower falls, even though we love it;
> | and a weed grows, even though we do not love it.
> |   --Dogen
>
============================================================================
===
>
>