pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bill Moran <wmoran@potentialtech.com>
To: Eric Chamberlain <Eric.Chamberlain@zonarsystems.com>
Cc: pgsql-php@postgresql.org
Subject: Re: Stored procedures, PDO, and PHP issue
Date: Wed, 19 Aug 2009 17:11:27 -0400
Message-ID: <20090819171127.57b19e4c.wmoran@potentialtech.com> (raw)
In-Reply-To: <A11E730E-82D7-4EE6-AD80-ECD95982D78A@zonarsystems.com>
References: <A11E730E-82D7-4EE6-AD80-ECD95982D78A@zonarsystems.com>

In response to Eric Chamberlain <Eric.Chamberlain@zonarsystems.com>:

> I'm having an issue calling a specific stored proc using PHP and PDO.   
> I have two procs with the same name and same number of parameters.   
> However, the parameter types are different.  When the below code is  
> called in PHP it always calls the varchar, varchar proc.  I can not  
> get it to call the integer, varchar proc.
> 
> Stored procedure definitions:
> boolean is_password_expired(i_user varchar, i_pass varchar)
> boolean is_password_expired(i_user_id integer, i_pass varchar)
> 
> $stmt = $db->prepare("SELECT is_password_expired(?, ?)");
> $stmt->bindValue(1, $userId, $hashPass, PDO::PARAM_INT);
> $stmt->execute();
> 
> This always returns false because it's passing the $userId, of say  
> "1", to the varchar, varchar proc.  I've tried using the following:
> 
> $stmt = $db->prepare("SELECT  
> is_password_expired(?::integer, ?::varchar)");
> 
> This completely fails.
> 
> $stmt->bindParam(1, $userId, $hashPass, PDO::PARAM_INT);
> 
> Same as bindValue result.
> 
> $stmt->execute(array($userId, $hashPass));
> 
> Same result.
> 
> Is there some way to inform PDO and Postgresql that I plan on using  
> the integer, varchar proc?  If so, how do I do this?  Thanks all!

I would expect what you're doing to work.  It works with the functional
interface.

What do the query logs on the server say?  Try turning full query logging
on and see what's actually getting run.

I see in another reply that you're getting a blank white screen.  This
tends to suggest that your debugging is configured wrong, or that PHP is
encountering a fatal error and coredumping or something similar.  Check
whatever logs are appropriate for evidence of this.  Check the HTTP error
log, as well as system error logs.

-- 
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/



view thread (10+ messages)  latest in thread

Message-ID: <20090819171127.57b19e4c.wmoran@potentialtech.com>
Permalink:  ../20090819171127.57b19e4c.wmoran@potentialtech.com/
Also on:    postgresql.org/message-id/20090819171127.57b19e4c.wmoran@potentialtech.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: wmoran@potentialtech.com, Eric.Chamberlain@zonarsystems.com
  Subject: Re: Stored procedures, PDO, and PHP issue
  In-Reply-To: <20090819171127.57b19e4c.wmoran@potentialtech.com>
  References: <A11E730E-82D7-4EE6-AD80-ECD95982D78A@zonarsystems.com> <20090819171127.57b19e4c.wmoran@potentialtech.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox