[Catching up on my old email, well at least sort of. Sorry for the
delay.]
On Wed, Feb 22, 2006 at 10:22:39AM -0500, [EMAIL PROTECTED] wrote:
> Will this still result in the closed DB connection that the "ROLLBACK
> RELEASE" used to give me?
ECPG just sends the queries to the backend the way you
[EMAIL PROTECTED] wrote:
>
>
>
>
>
> >I think you should omit the word "RELEASE" after the
> > "ROLLBACK".
>
> Will this still result in the closed DB connection that the "ROLLBACK
> RELEASE" used to give me?
No, it will not. I see way to do that anymore using a single statement.
--
[EMAIL PROTECTED] wrote:
> I'm relatively new to database programming & I've inherited a system to
> maintain that contains lots of embedded SQL. I'm attempting to port my C
> source code from RH 7.2 (with ecpg 2.8.0) to Mandrake 10.0 (with ecpg
> 4.1.1). ecpg 4.1.1 is generating an error which
[EMAIL PROTECTED] writes:
>>I think you should omit the word "RELEASE" after the
>> "ROLLBACK".
>
> Will this still result in the closed DB connection that the "ROLLBACK
> RELEASE" used to give me?
I don't know--you should check the current docs for ECPG (I don't use
it).
-Doug
cc
AM
Subject
Re: [GENERAL] ecpg error -->
DbPg_cre_sect_buf.pgc:1334: ERROR:
[EMAIL PROTECTED] writes:
> I'm relatively new to database programming & I've inherited a system to
> maintain that contains lots of embedded SQL. I'm attempting to port my C
> source code from RH 7.2 (with ecpg 2.8.0) to Mandrake 10.0 (with ecpg
> 4.1.1). ecpg 4.1.1 is generating an error whic
I'm relatively new to database programming & I've inherited a system to
maintain that contains lots of embedded SQL. I'm attempting to port my C
source code from RH 7.2 (with ecpg 2.8.0) to Mandrake 10.0 (with ecpg
4.1.1). ecpg 4.1.1 is generating an error which I did not get on the
RH7.2 sy