> 5. Because of the way the expression is parsed (looking for closing > parenth), this will choke if you try and put a function in there. Would > it be better to use curly braces '{expr}' or another character to mark > the expression?
I lie! pgpgsql_read_expression() is smarter than that! However, I do have another problem. If the value of the expr changes inside a loop to a fieldname of a different type, it dies with the "type of \"%s\" does not match that when preparing the plan" message, which is quite true: it obviously doesn't. Just setting expectedtypeoid to InvalidOid bombs the whole thing :( Hrm.... the "best made plans" and all that... Matt ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match