Subject | Stored procs and views |
---|---|
Author | Claudio Valderrama C. |
Post date | 2001-02-09T07:47:15Z |
Hello, can anyone explain why IB doesn't allow procedures to be used in
views? I'm trying to find if there's some sensible reason. Example:
create view v0 as
select a from myproc(b);
=> fails, but
create view v1 as
select * from rdb$database
where (select a from myproc(b)) > 3
=> succeeds
The docs say procs's aren't accepted inside a view definition. IB enforces
the rule in the FROM clause but accepts a proc happily in the WHERE clause.
So what's the tale? Is there any architectural reason why procedures can't
be used in views? Should we consider a proc in the WHERE part of a view a
feature or a bug that comes from lack of validation?
Thanks for comments. I want to understand if there's some important
limitation behind this rule.
C.
---------
Claudio Valderrama C.
Ingeniero en Informática - Consultor independiente
http://www.cvalde.com
views? I'm trying to find if there's some sensible reason. Example:
create view v0 as
select a from myproc(b);
=> fails, but
create view v1 as
select * from rdb$database
where (select a from myproc(b)) > 3
=> succeeds
The docs say procs's aren't accepted inside a view definition. IB enforces
the rule in the FROM clause but accepts a proc happily in the WHERE clause.
So what's the tale? Is there any architectural reason why procedures can't
be used in views? Should we consider a proc in the WHERE part of a view a
feature or a bug that comes from lack of validation?
Thanks for comments. I want to understand if there's some important
limitation behind this rule.
C.
---------
Claudio Valderrama C.
Ingeniero en Informática - Consultor independiente
http://www.cvalde.com