From: | "Lori Pate" <lpate(at)opushealthcare(dot)com> |
---|---|
To: | <pgadmin-support(at)postgresql(dot)org> |
Subject: | Column name validation in embedded query. |
Date: | 2005-11-07 14:55:31 |
Message-ID: | 26EF234CFA0A61499BE54B08447FE397D30383@sleepy.opushealthcare.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
I am using pgAdmin III, PostgreSQL tools, Version 1.2.0 Beta on Windows XP Pro.
The following query, when executed as a stand alone query returns an error, correctly, that the column name is not valid:
Query A) Select patientorder_key from patientorder where visit_key = 250314 and provider_key = 301;
The correct syntax should be:
Query B) Select patientorder.key from patientorder where visit_key = 250314 and provider_key = 301;
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;
This resulted in massive amounts of data being deleted erroneously.
I believe this is a bug.
Lori E. Pate
Quality Assurance Engineer
Opus Healthcare Solutions, Inc.
12301 Research Blvd.
Bldg. IV, Suite 200
Austin, Texas 78759
Phone: 512.336.4562
E-Mail: lpate(at)opushealthcare(dot)com
AIM: loripate0508
http://www.opushealthcare.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Hendrik-Jan Heins | 2005-11-07 19:32:21 | pgadmin3 1.4.0 for Mandriva |
Previous Message | Joost Kraaijeveld | 2005-11-07 13:50:55 | Re: PgAdmin 1.4.0 Debian SArge AMD64 debs available (Debian-AMD removed) |