Skip site navigation (1) Skip section navigation (2)

Re: ecpg Oracle compatibility issue

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Roland Karch <rdkarch(at)immd3(dot)informatik(dot)uni-erlangen(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: ecpg Oracle compatibility issue
Date: 2002-12-12 21:49:30
Message-ID: 200212122149.gBCLnVo02381@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
I applied the attached patch. Your version looked like it would have
doubled the double-quotes.  As you mentioned, you couldn't get bison to
work, so you weren't able to test it.  Please look over this patch and
make sure it is correct.  Also check the other use of ECPGdisconnect(). 
Is that correct?  Does it need "CURRENT"?

---------------------------------------------------------------------------

Roland Karch wrote:
> Hello together,
> 
> While porting my TPC-C implementation from Oracle, I discovered the
> attached problem with the EXEC SQL COMMIT RELEASE statement.
> 
> Bye,
> Roland
> 

[ Attachment, skipping... ]

> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073


In response to

Responses

pgsql-bugs by date

Next:From: Thomas O'ConnellDate: 2002-12-12 21:58:09
Subject: time and current_time default formats
Previous:From: Tom LaneDate: 2002-12-12 19:20:46
Subject: Re: initdb segfaulting.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group