Aristide Aragon <[EMAIL PROTECTED]> writes:
> On Thu, Feb 22, 2001 at 07:49:56PM -0800, Ian Lance Taylor wrote:
> > Aristide Aragon <[EMAIL PROTECTED]> writes:
> >
> > > I have to do some programming in C or C++ and PostgreSQL.
> > SPI is only for stor
Aristide Aragon <[EMAIL PROTECTED]> writes:
> I have to do some programming in C or C++ and PostgreSQL.
> Having not ever done this before, I opened the documentation (in my machine,
>/usr/local/pgsql/doc) and read about the options I had. SPI, libpq, libpq++ and ecpg.
>I don't want, if possibl
Joseph Shraibman <[EMAIL PROTECTED]> writes:
> > Note that this all implies that when walking through the index to find
> > heap tuples, you must check the current validity of each heap tuple.
> > It is normal for an index tuple to point to a heap tuple which has
> > been deleted.
>
>
> > >
> >
Joseph Shraibman <[EMAIL PROTECTED]> writes:
> > > I understand that keeping different views for different open
> > > transactions can be difficult, but after a transaction that updates a
> > > row is over why isn't the row marked as 'universally visible' for all
> > > new transactions until ano
Joseph Shraibman <[EMAIL PROTECTED]> writes:
A caveat on this reply: I've been studying the Postgres internals, but
I have not mastered them.
> I understand that keeping different views for different open
> transactions can be difficult, but after a transaction that updates a
> row is over why
"Thomas T. Thai" <[EMAIL PROTECTED]> writes:
> why does this happen?
>
> -- Forwarded message --
> Date: Thu, 8 Feb 2001 10:46:59 -0600 (CST)
> From: Mail Delivery Subsystem <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Returned mail: see transcript for details
>
> The
Jan Wieck <[EMAIL PROTECTED]> writes:
> Ian Lance Taylor wrote:
> >
> > I have a patch which adds support for cursors in PL/pgSQL. If anybody
> > is interested, I can provide that patch against either 7.0.3 or the
> > current CVS sources. I have sent it
Camm Maguire <[EMAIL PROTECTED]> writes:
> Greetings! Just read that this functionality is planned for the
> future. Can 7.1 have cursors in pgsql functions, for example?
No, it can't.
I have a patch which adds support for cursors in PL/pgSQL. If anybody
is interested, I can provide that pat
