psycopg2 not using appropriate type? - Mailing list psycopg

From Wells Oliver
Subject psycopg2 not using appropriate type?
Date
Msg-id AANLkTim1j6mzqEQUWfNSU41m9r8ayP6HO9rb5x5SD54P@mail.gmail.com
Whole thread Raw
Responses Re: psycopg2 not using appropriate type?
List psycopg
It seems when I use callproc(), psycopg2 isn't properly casting strings as text or character varying.

For example:

values = [pid, 4, 4, 'bureau pitcher ama', 0, 130, row['report_dte'], row['report_dte'], 1, 1, 1, None, None, 'published', row['report_dte']]
cur.callproc('header', values)

Yields:

psycopg2.ProgrammingError: function basetek_scouting.insert_report_header(integer, integer, integer, unknown, integer, integer, unknown, unknown, integer, integer, integer, unknown, unknown, unknown, unknown) does not exist
LINE 1: SELECT * FROM header(509952,4.

First, the "bureau pitcher ama" is unknown instead of text/character, and row["report_dte"] are all unknown, where they are date types in the database, and datetime.date objects in python.

Any idea? Using python 2.6.5.

--
Wells Oliver
wellsoliver@gmail.com

psycopg by date:

Previous
From: Barend Köbben
Date:
Subject: Re: psycopg used in a ASP page fails
Next
From: Federico Di Gregorio
Date:
Subject: Re: psycopg2 not using appropriate type?