Commitc8e9935

committed

Fix failure to propagate collation in negate_clause().

Turns out it was this, and not so much plpgsql, that was at fault in StefanHuehner's collation-error-in-a-trigger bug report of a couple weeks ago.

1 parent9b19c12 commitc8e9935Copy full SHA for c8e9935

File tree

-0

lines changed

-0

lines changed

Lines changed: 3 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -104,6 +104,8 @@ negate_clause(Node *node)`
`104`	`104`	`newopexpr->opfuncid=InvalidOid;`
`105`	`105`	`newopexpr->opresulttype=opexpr->opresulttype;`
`106`	`106`	`newopexpr->opretset=opexpr->opretset;`
	`107`	`+newopexpr->opcollid=opexpr->opcollid;`
	`108`	`+newopexpr->inputcollid=opexpr->inputcollid;`
`107`	`109`	`newopexpr->args=opexpr->args;`
`108`	`110`	`newopexpr->location=opexpr->location;`
`109`	`111`	`return (Node*)newopexpr;`
`@@ -126,6 +128,7 @@ negate_clause(Node *node)`
`126`	`128`	`newopexpr->opno=negator;`
`127`	`129`	`newopexpr->opfuncid=InvalidOid;`
`128`	`130`	`newopexpr->useOr= !saopexpr->useOr;`
	`131`	`+newopexpr->inputcollid=saopexpr->inputcollid;`
`129`	`132`	`newopexpr->args=saopexpr->args;`
`130`	`133`	`newopexpr->location=saopexpr->location;`
`131`	`134`	`return (Node*)newopexpr;`

Comments

(0)