Shreyas Kaushik wrote: >> Dan Debrunner wrote: >> The dml162 test from the >> nist suite fails to create a view that previously was created ok. This >> dml162 issue would need to be resolved before the patch could be >> accepted. >> >> > With the changes the fully qualified column name should be given or it > would take the default schema and the > default schema does not have what the test is looking for. Since > everything is prefixed with "HU." so should the > column in question. With that change it works fine. Sending a patch for > this also.
> Index: dml162.sql > =================================================================== > --- dml162.sql (revision 153026) > +++ dml162.sql (working copy) > @@ -21,7 +21,7 @@ > CREATE VIEW BLIVET (CITY, PNUM, EMPNUM, EMPNAME, GRADE, > HOURS, PNAME, PTYPE, BUDGET) AS > --0 HU.STAFF NATURAL JOIN HU.WORKS NATURAL JOIN HU.PROJ; > - SELECT PROJ.CITY, HU.PROJ.PNUM, HU.STAFF.EMPNUM, EMPNAME, GRADE, > HOURS, PNAME, PTYPE, BUDGET > + SELECT HU.PROJ.CITY, HU.PROJ.PNUM, HU.STAFF.EMPNUM, EMPNAME, GRADE, > HOURS, PNAME, PTYPE, BUDGET > FROM HU.STAFF JOIN HU.WORKS ON (HU.STAFF.EMPNUM=HU.WORKS.EMPNUM) JOIN > HU.PROJ ON (HU.PROJ.PNUM=HU.WORKS.PNUM AND HU.PROJ.CITY=HU.STAFF.CITY) > ; > -- PASS:0863 If view created successfully? Anyone else have any comments on this patch, was the view in dml162 being created incorrectly before? The view has been modified from the original NIST code, so maybe it was always a hidden bug in Cloudscape. Dan.
