Commented by: Alice F. Bird (firebirds)

Date: 2004-09-05 18:14
Sender: dimitr
Logged In: YES
user_id=61270

If anyone thinks that a PLAN option should be available in
views, please create a new feature request. I consider this
issue closed.

Commented by: Alice F. Bird (firebirds)

Date: 2003-01-21 10:28
Sender: dimitr
Logged In: YES
user_id=61270

I tend to think that a PLAN option should be disallowed in the VIEW
declaration until this issue is fixed. We've already done the same thing for
FIRST/SKIP in v1.5, so why should PLAN be different? Once all these
problems are solved, we will allow these options again.

Commented by: @pavel-zotov

What's the current state of issue about forbidden PLAN specification in a view DDL ?

As far as I see one may still to specify PLAN but it's ignored (as before):

SQL> recreate table test(x int unique using index test_x_unq);
SQL> recreate view v_test as select x from test t where x = 0 plan (t natural);
SQL> insert into test select row_number()over()-5 from rdb$types rows 10;
SQL> commit;

SQL> set plan on;
SQL> select x from test t where x = 0 plan (t natural);

PLAN (T NATURAL)

       X

============
0

SQL> select x from v_test t where x = 0;

PLAN (T T INDEX (TEST_X_UNQ)) ------------- ? Why ?

       X

============
0

SQL> select x from v_test t where x = 0 plan (t natural); -- this plan was included into this view DDL when it was created. We have to repeat it again here ?

PLAN (T T NATURAL)

       X

============
0

PS. Checked on: WI-V2.5.6.26980; WI-V3.0.0.32380.