When I create a view that calls a function, function reference is replaced by its formula (simplified if possible).
Is there a way to prevent it?
Example:
CREATE FUNCTION f (x NUMERIC) RETURN NUMERIC AS
BEGIN
RETURN 2*x;
END;
CREATE VIEW v_f AS
SELECT f(1) AS v;
The actual code of this view is:
CREATE VIEW v_ft
AS
SELECT 2 AS v FROM v_catalog.dual
@OP,
Per Vertica documentation, this is the expected behavior.
Documentation
MY question is why would you want to prevent this behavior?
Just want to understand the use-case.
OK, is there a way to override this? I'd like Vertica to keep and run the view exactly as I've coded.
I understand the importance of flattening for performance, but a choice would be welcome - much like you can modify the behaviour of optimizer in other databases.
As for a use-case - I don't think it really matters.
One of fundaments of functions in programming is that they enclose a piece of code, which can be easily modified (fixed, developed further).
With forced flattening, functions in Vertica are just code shorthands. I find this design choice very weird and limiting...
Basically, I'll have to script all objects in the database and overwrite everything that references a modified function.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
