Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Matthias Apitz <guru(at)unixarea(dot)de>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
Date: 2020-05-13 14:15:42
Message-ID: 31687.1589379342@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Matthias Apitz <guru(at)unixarea(dot)de> writes:
> El día Dienstag, Mai 12, 2020 a las 08:01:15 -0400, Tom Lane escribió:
>> Not an unreasonable suggestion, but it'd be more likely to happen if
>> you send in a patch ;-).

> as the first argument to ECPGdo() is of type int we can not do a hack
> like "__LINE__:"__FILE__ (i.e. concatenating line number and filename
> into one string. We have to change the call interface function ECPGdo()
> and add a string argument.

Yeah, now that you mention that, this was discussed before. We cannot
change the signature of ECPGdo as that would break existing client
binaries. We could leave it alone (and unused by newer compilations)
if we add a new entry point, though. "ECPGnewdo()", anybody?

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Basques, Bob (CI-StPaul) 2020-05-13 14:18:24 RE: Enforcing uniqueness on [real estate/postal] addresses
Previous Message Rich Shepard 2020-05-13 14:01:15 RE: Enforcing uniqueness on [real estate/postal] addresses