| From: | "David Joyner" <d4ljoyn(at)yahoo(dot)com> |
|---|---|
| To: | <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | libpq++ |
| Date: | 2002-01-09 14:01:33 |
| Message-ID: | 002601c19916$836921c0$01854094@bluepoles |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
I recently got the latest source from cvs. I think there's a bug in
pgtransdb.cc. The pgCommitted flag will never be true after the implicit
BeginTransaction called by creating a PgCursor.
I ran testlibpq3.cc with logging enabled -- sure enough when using a cursor
ABORT is always executed in PgTransaction destructor. When fetching this
has no effect, but still.
Am I missing something? Does one need to somehow explicitly call
EndTransaction? If so, how? That's a protected member, and nothing in
PgCursor seems to call it.
Also, PgCursor is the only module I can see that has std:: namespace
dependency. Why?
Thanks for your time
Dave Joyner
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Nelson | 2002-01-09 17:06:52 | [ECPG] generates bad code on declare/open |
| Previous Message | Tom Lane | 2002-01-08 00:32:42 | Re: libpq doing strange things |