DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
	b=aSfbp/Wnx50fOrmf7XaC02R5AN42hxJOBN3Inlks+34HqYGCPUrVUM8Kyd2XOh9uT30yMS5KyjrF31rSobBnjh5WCLZTSCLHJNKYsg0+5a3p7NVrVy7ieQZNE//3sd0UZ7L0QjgWpvCR8cdfzrVRyP6BrQc99/tlpzIQeq4dwjA=
Message-ID: <fdb4b04c0608110745t6dea55aeod40cf8e19a283dc1@mail.gmail.com>
Date: Fri, 11 Aug 2006 09:45:36 -0500
From: "Chris Lukenbill" <chris@blendinteractive.com>
To: pgsql-sql@postgresql.org
Subject: Can't find which return type is incorrect.
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_47072_29426166.1155307536915"

------=_Part_47072_29426166.1155307536915
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Alright.  I have a very large amount of columns being returned by this
stored procedure that I ported from MS SQL to Postgres.  Now the problem I'm
having is that when the select * from sp_whatever(1,0,3) as ( foo int, bar
int, etc.) is executed the error "wrong record type supplied in RETURN NEXT
CONTEXT".  Now this immediately red flagged me to look at the types that I
was returning and verify that those were the types that I was catching in
the as statement.  I went through to verify all of the variables and they
are all correct as far as both name and the exact type.  Therefore there are
only a few things left that I'm thinking could be the problem.

1. Too many variables returned (there are 44 variables being returned).
2. Some of the variables that are smallint in the select statement also do a
if isnull type of logic that will return zero if they are null.  (is that
zero not coming back as a smallint then?)
3. What I'm declaring as a variable type in postgresql isn't the variable
type in PHP.  The following are the different types of variables that I use:
INT
SMALLINT
BIGINT (when I do a count(*))
VARCHAR(xx)
TEXT
TIMESTAMP
NUMERIC(19,2)


Now the two there that I'm skeptical about are the timestamp and the
numeric.

Thanks ahead of time for any ideas,
Chris

------=_Part_47072_29426166.1155307536915
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Alright.&nbsp; I have a very large amount of columns being returned by this stored procedure that I ported from MS SQL to Postgres.&nbsp; Now the problem I'm having is that when the select * from sp_whatever(1,0,3) as ( foo int, bar int, etc.) is executed the error   &quot;wrong record type supplied in RETURN NEXT
CONTEXT&quot;.&nbsp; Now this immediately red flagged me to look at the types that I was returning and verify that those were the types that I was catching in the as statement.&nbsp; I went through to verify all of the variables and they are all correct as far as both name and the exact type.&nbsp; Therefore there are only a few things left that I'm thinking could be the problem.
<br><br>1. Too many variables returned (there are 44 variables being returned).<br>2. Some of the variables that are smallint in the select statement also do a if isnull type of logic that will return zero if they are null.&nbsp; (is that zero not coming back as a smallint then?)
<br>3. What I'm declaring as a variable type in postgresql isn't the variable type in PHP.&nbsp; The following are the different types of variables that I use:<br>INT<br>SMALLINT<br>BIGINT (when I do a count(*))<br>VARCHAR(xx)
<br>TEXT<br>TIMESTAMP<br>NUMERIC(19,2)<br><br><br>Now the two there that I'm skeptical about are the timestamp and the numeric.<br><br>Thanks ahead of time for any ideas,<br>Chris<br><br>

------=_Part_47072_29426166.1155307536915--