Received: from pille.addcom.de (qmailr@h-62.96.128.34.host.de.colt.net [62.96.128.34]) by hub.org (8.9.3/8.9.3) with SMTP id PAA58671 for ; Wed, 29 Dec 1999 15:26:52 -0500 (EST) (envelope-from michael@fam-meskes.de) Received: (qmail 31672 invoked from network); 29 Dec 1999 20:26:42 -0000 Received: from h-62.96.160.43.host.de.colt.net (62.96.160.43) by pille.addcom.de with SMTP; 29 Dec 1999 20:26:42 -0000 Received: (from michael@localhost) by tanja.fam-meskes.de (8.9.3/8.9.0/Debian/GNU) id NAA00412; Wed, 29 Dec 1999 13:34:01 +0100 Date: Wed, 29 Dec 1999 13:34:01 +0100 From: Michael Meskes To: "S.F. Lee" Cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] manipulate array wiht ecpg Message-ID: <19991229133401.B324@fam-meskes.de> Mail-Followup-To: "S.F. Lee" , pgsql-interfaces@postgreSQL.org References: <19991229064052.14930.rocketmail@web221.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In-Reply-To: <19991229064052.14930.rocketmail@web221.mail.yahoo.com>; from sflee_tw@yahoo.com on Tue, Dec 28, 1999 at 10:40:52PM -0800 On Tue, Dec 28, 1999 at 10:40:52PM -0800, S.F. Lee wrote: > After getting temp from exec sql select ....., I use > strtol() to convert temp.a into a integer array, and > it works! I now have another problem that is I can get Still I would prefer a better handling by ecpg. :-) > the tuples by sqlca.sqlerrd[2], but how can I get the > type of each field that has been selected? In libpq++ > FieldType(n) can get the type of field, how about in > ecpg? I do not know a way other than querying the data dictionary. What does the standard say? Should we return such info? What do other RDBMS do in this scenario? Is there a way I can give this info back anyway. Right now I cannot imagine one since we give back the whole tuple at once. Where shall we store these per attribute infos? Michael -- Michael Meskes | Go SF 49ers! Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire! Tel.: (+49) 2431/72651 | Use Debian GNU/Linux! Email: Michael@Fam-Meskes.De | Use PostgreSQL!