From: | Jan Wieck <janwieck(at)yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jan Wieck <janwieck(at)yahoo(dot)com>, Joep deVocht <joep(at)masktools(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Small question |
Date: | 2002-03-22 19:30:00 |
Message-ID: | 200203221930.g2MJU0316307@saturn.janwieck.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Jan Wieck <janwieck(at)yahoo(dot)com> writes:
> >> It seems like it might be possible for libpq (or other clients) to keep
> >> track of the transaction state by paying attention to BEGIN, COMMIT,
> >> ABORT command-completion tags and ERROR messages, but I haven't worked
> >> through the details.
>
> > PQexec(c, "BEGIN; SELECT now()");
>
> > Will there even be a BEGIN command tag sent?
>
> Yes. PQexec doesn't tell you about it, but one comes through. (This
> is certainly true in current sources, and I believe has always been true.)
>
> It'd be nastier if we allowed functions to change the transaction-block
> state, but we don't...
Well, then we don't need a protocol change. Libpq and other
interface libraries could keep track of it without.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-03-22 19:52:29 | Re: Small question |
Previous Message | Tom Lane | 2002-03-22 19:26:34 | Re: Small question |