Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP id 8FD214759EB
	for <pgsql-interfaces@postgresql.org>;
	Fri, 19 Jul 2002 17:24:28 -0400 (EDT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g6JLOSVk015459;
	Fri, 19 Jul 2002 17:24:28 -0400 (EDT)
To: Daniel Kelley <dkelley@otec.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: ecpg & host variables 
In-reply-to: <Pine.BSF.4.20L2.0207191555500.34939-100000@mx1.gc.ny.otec.com> 
References: <Pine.BSF.4.20L2.0207191555500.34939-100000@mx1.gc.ny.otec.com>
Comments: In-reply-to Daniel Kelley <dkelley@otec.com>
	message dated "Fri, 19 Jul 2002 17:02:53 -0400"
Date: Fri, 19 Jul 2002 17:24:28 -0400
Message-ID: <15458.1027113868@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200207/113
X-Sequence-Number: 2922

Daniel Kelley <dkelley@otec.com> writes:
> ... which yields the following error from ecpg:
> postgres.pgc:15: ERROR: invalid datatype 'typedef'

I believe ecpg was just recently fixed to support typedefs.  You might
try using the ecpg from a recent snapshot.  (AFAIK it should be stable
enough for production use, though I'd not recommend using anything else
from development tip ...)

			regards, tom lane