Subject | Re: [firebird-support] Views / performance |
---|---|
Author | Helen Borrie |
Post date | 2004-03-31T02:02:17Z |
At 11:21 PM 30/03/2004 +0200, you wrote:
There *is* extra cost in the optimizer with views. In the
"aim-once-shoot-many" scenario you won't notice it. If your application
flow prepares every time, the cost is likely to become noticeable.
AFAIR, the only times when it was expressed as "something to worry about"
was in the context of questions like "Is there any performance reason not
to encapsulate my entire application sets requirements into views so that I
can use a Delphi TTable for everything and forget about learning how SQL
works?" That WILL have a horrible performance cost. :-))
Views are great for packaging curly queries.
/heLen
>Thanks, but that's strange, I don't know where I read it that views could beIt has been mentioned from time to time...
>a problem when updating data....
There *is* extra cost in the optimizer with views. In the
"aim-once-shoot-many" scenario you won't notice it. If your application
flow prepares every time, the cost is likely to become noticeable.
AFAIR, the only times when it was expressed as "something to worry about"
was in the context of questions like "Is there any performance reason not
to encapsulate my entire application sets requirements into views so that I
can use a Delphi TTable for everything and forget about learning how SQL
works?" That WILL have a horrible performance cost. :-))
Views are great for packaging curly queries.
/heLen