X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BB187D1B198 for ; Fri, 2 Jul 2004 04:10:10 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 42397-09 for ; Fri, 2 Jul 2004 07:10:08 +0000 (GMT) Received: from skyhouseconsulting.com (skyhouseconsulting.com [216.93.161.184]) by svr1.postgresql.org (Postfix) with ESMTP id D5570D1B174 for ; Fri, 2 Jul 2004 04:10:05 -0300 (ADT) Received: from amadeus ([202.88.158.57]) by skyhouseconsulting.com (8.12.10/8.12.10) with ESMTP id i6279vDv021430; Fri, 2 Jul 2004 02:09:59 -0500 (CDT) (envelope-from jason@openinformatics.com) Received: from jasons by amadeus with local (Exim 3.35 #1 (Debian)) id 1BgIB3-0003C3-00; Fri, 02 Jul 2004 12:39:41 +0530 To: pgsql-interfaces@postgresql.org Cc: dbi-dev@perl.org Subject: DBD::Pg and $sth->{ParamValues} From: jason_e_stewart@users.sourceforge.net Date: Fri, 02 Jul 2004 12:39:40 +0530 Message-ID: <878ye2c2bv.fsf@openinformatics.com> User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200407/19 X-Sequence-Number: 5025 Hey, What is the status of the this attribute? I would like to help implement the code (since I need it for my application). But I'm a bit confused about what the status of prepared statements is in the code. I'm assuming the the dbd_st_execute() in dbdimp.c is the latest code used and that prescan_stmt.c isn't being used. I'm not a great C coder anymore so pardon my ignorance. From my reading of the code, there is an array: const char **paramValues; which is dynamically allocated: paramValues = calloc(imp_sth->numphs, sizeof(*paramValues)); but it is never freed, isn't that a memory leak? I'm wondering about this because in order to make the ParamValues attribute work, I'll need to make that array part of the statement handle - and I don't want to be keeping track of memory that is going to vanish out from underneath me. Cheers, jas.