- Notifications
You must be signed in to change notification settings - Fork5
Commit9676b01
committed
Allow USING and INTO clauses of plpgsql's EXECUTE to appear in either order.
Aside from being more forgiving, this prevents a rather surprising misbehaviorwhen the "wrong" order was used: the old code didn't throw a syntax error,but absorbed the INTO clause into the last USING expression, which then didstrange things downstream.Intentionally not changing the documentation; we'll continue to advertiseonly the "standard" clause order.Backpatch to 8.4, where the USING clause was added to EXECUTE.1 parentf4b4a46 commit9676b01
1 file changed
+34
-19
lines changedLines changed: 34 additions & 19 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
8 | 8 |
| |
9 | 9 |
| |
10 | 10 |
| |
11 |
| - | |
| 11 | + | |
12 | 12 |
| |
13 | 13 |
| |
14 | 14 |
| |
| |||
1642 | 1642 |
| |
1643 | 1643 |
| |
1644 | 1644 |
| |
1645 |
| - | |
1646 |
| - | |
1647 |
| - | |
1648 |
| - | |
1649 |
| - | |
1650 |
| - | |
1651 |
| - | |
1652 |
| - | |
1653 |
| - | |
1654 |
| - | |
1655 |
| - | |
1656 |
| - | |
| 1645 | + | |
| 1646 | + | |
| 1647 | + | |
| 1648 | + | |
| 1649 | + | |
| 1650 | + | |
| 1651 | + | |
| 1652 | + | |
1657 | 1653 |
| |
1658 |
| - | |
| 1654 | + | |
| 1655 | + | |
| 1656 | + | |
| 1657 | + | |
| 1658 | + | |
| 1659 | + | |
| 1660 | + | |
| 1661 | + | |
| 1662 | + | |
1659 | 1663 |
| |
1660 |
| - | |
1661 |
| - | |
1662 |
| - | |
1663 |
| - | |
1664 |
| - | |
| 1664 | + | |
| 1665 | + | |
| 1666 | + | |
| 1667 | + | |
| 1668 | + | |
| 1669 | + | |
| 1670 | + | |
| 1671 | + | |
| 1672 | + | |
| 1673 | + | |
| 1674 | + | |
| 1675 | + | |
| 1676 | + | |
| 1677 | + | |
| 1678 | + | |
| 1679 | + | |
1665 | 1680 |
| |
1666 | 1681 |
| |
1667 | 1682 |
| |
|
0 commit comments
Comments
(0)