[Libpqxx-general] Unnamed prepared statements

[Trigve Siver]

> From: Jeroen T. Vermeulen <jtv at xs4all.nl>

> To: Trigve Siver <trigves at yahoo.com>
> Cc: libpqxx-general at pgfoundry.org
> Sent: Friday, August 14, 2009 9:18:33 PM
> Subject: Re: [Libpqxx-general] Unnamed prepared statements
> 
> On Sat, August 8, 2009 13:15, Trigve Siver wrote:
> 
> >> Hi there,
> >> I've been trying to find where my problem with unnamed preparedt stmts
> >> lie. Oh
> >> christ, have tried it for 5 hours. My problem is bit complicated because
> >> I
> >> cannot simple isolate it. But I try to describe it. I'm preparing (and
> >> using it)
> >> unnamed prepared statement (UPS) with definition named def1 (with some
> >> parameters).
> >
> > I found I was wrong, the second statement without params wasn't created
> > so, ignore it. I've removed it in this mail.
> 
> Hi Trigve,
> 
> I'm sorry for not noticing your messages for so long.  From your message I
> can't quite figure out if you're still having a problem or not.

Hi, yes problem still persist. Sorry for some misleading info here is the problem description:

I've been trying to find where my problem with unnamed preparedt stmts lie. Oh christ, have tried it for 5 hours. My problem is bit complicated because I cannot simple isolate it. But I try to describe it. I'm preparing (and using it) unnamed prepared statement (UPS) with definition named def1 (with some parameters). Then I create the same UPS (as the first) with definition of def1 and  call it and I've got the error "unnamed prepared statement does not exist" from  Postgres. This is some basic scheme in which I encounter the problem. The fix is  attached.  I found that in rev. 1553 there was some update in UPS's. I've added  "i->second.registered = false;" in "pqxx::prepare::declaration 
pqxx::connection_base::prepare". I havent go deeper but it seems that it works.  So can someone shed some light on this?

> 
> Jeroen

Trigve