Re: Fw: ecpg error --> DbPg_cre_sect_buf.pgc:1334: ERROR: syntax error at or near "RELEASE"

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: jason(dot)ctr(dot)alburger(at)faa(dot)gov
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Fw: ecpg error --> DbPg_cre_sect_buf.pgc:1334: ERROR: syntax error at or near "RELEASE"
Date: 2006-03-16 08:42:32
Message-ID: 20060316084232.GD24681@1
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

[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, jason(dot)ctr(dot)alburger(at)faa(dot)gov 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 write them. It
does some parsing so you can be noticed if there are syntax errors. It
also does some translations to get the C variables into the SQL code and
vica versa, but all other statement with the exception of
prepare/execute are transferred as-is. Or at least that should be the
case. :-)

So to see if ROLLBACK has the behaviour you need you have to check the
backend documentation.

Michael

--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Magnus Hagander 2006-03-16 09:09:25 Re: What's a good default encoding?
Previous Message Martijn van Oosterhout 2006-03-16 08:36:59 Re: What's a good default encoding?