From c74d8a7708d188f06e0c8bdf340847084915138f Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 14 Aug 2009 13:12:21 +0000 Subject: [PATCH] Domain support in PL/Python When examining what Python type to convert a PostgreSQL type to on input, look at the base type of the input type, otherwise all domains end up defaulting to string. --- src/pl/plpython/plpython.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pl/plpython/plpython.c b/src/pl/plpython/plpython.c index c52e67e662..ee94b637fe 100644 --- a/src/pl/plpython/plpython.c +++ b/src/pl/plpython/plpython.c @@ -1,7 +1,7 @@ /********************************************************************** * plpython.c - python as a procedural language for PostgreSQL * - * $PostgreSQL: pgsql/src/pl/plpython/plpython.c,v 1.124 2009/08/13 20:50:05 petere Exp $ + * $PostgreSQL: pgsql/src/pl/plpython/plpython.c,v 1.125 2009/08/14 13:12:21 petere Exp $ * ********************************************************************* */ @@ -1641,7 +1641,7 @@ PLy_input_datum_func2(PLyDatumToOb *arg, Oid typeOid, HeapTuple typeTup) arg->typbyval = typeStruct->typbyval; /* Determine which kind of Python object we will convert to */ - switch (typeOid) + switch (getBaseType(typeOid)) { case BOOLOID: arg->func = PLyBool_FromString; -- 2.40.0