Re: [BUGS] FW: [pgadmin-support] Column name validation in embedded query.

#1

"Lori Pate" <lpate (AT) opushealthcare (DOT) com> writes:

Quote:

However, when the query with the incorrect column name (Query A) is
embedded in a where clause, column validation does not happen, no error
is displayed, and PGAdmin apparently ignores the where clause all
together, resulting in complete data deletion, as if there were no where
clause:

Begin;
Delete from testorder where patientorder_key in
(Select patientorder_key from patientorder where visit_key = 250314 and
provider_key = 301);
End;

Unfortunately for you, that IS a valid SQL command.

In a subselect like that, unqualified column names are supposed to be
sought first in the subselect (ie, table patientorder) and then in the
outer query (table testorder). So patientorder_key will be found as an
outer reference to testorder. The fact that this renders the query a
bit silly does not change the fact that it's valid per spec.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: [BUGS] FW: [pgadmin-support] Column name validation in embedded query.

mailing.database.pgsql-bugs mailing.database.pgsql-bugs

Re: [BUGS] FW: [pgadmin-support] Column name validation in embedded query. - 11-08-2005 , 08:45 AM