#41 view parsing problems

[Albert Tumanov]

By: Strangerke

1) The source code of one of the views is the following :

CREATE OR REPLACE FORCE VIEW bt.v_advanced_search_reqst
(holdr_id, reqst_id)
AS
SELECT t_fil.holdr_id, t_reqst.reqst_id
FROM bt.t_fil, bt.t_reqst
WHERE t_fil.fil_id = t_reqst.fil_id;

The FORCE keyword is not part of your grammar.
2) In the select clause, you can use an optional 'AS'
in order to rename the column. The parser doesn't
accept this. example : "select null as test from dual"
is equivalent to "select null test from dual".
3) the joins definition are not handled. example :
SELECT a.name, b.ref_nbr
FROM holder a left join file b on a.holder_id = b.holder_id
4) in the view scripts, the ORDER BY clause is not handled
5) in the views scripts, the presence in the SELECT
statement of a DISTINCT seems to screw up everything
6) in the SELECT / sub-selects statement, the COUNT(*)
function is not handled.
7) in the WHERE clause, IS (NOT) NULL is not handled
8) in the WHERE clause, the implicit out join column1 =
column2 (+) doesn't work