Pavel Stehule <[EMAIL PROTECTED]> writes:
> When I declare variable with same name as field of table, then I
> have a problem with insert cmd in plpgsql procedure.
Don't do that.
> Is it plpgsql error or my bug?
You could argue it either way, perhaps, but it's unlikely to get
changed. In general plpgsql cannot tell whether a variable name
appearing in a SQL command ought to be substituted for or not, and so it
just always does it. I think trying to be smart would create as many
pitfalls as it'd solve. The best practice is not to use plpgsql
variable names that match table or field names you need to access in the
same procedure.
regards, tom lane
---------------------------(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
