having only a single view would not be more index friendly ;)

Instead of embedding common table expressions or sub-queries into view
definitions it is far easier to create permanent views instead, which can be
used whenever they are needed.

I didn't take care about the double pipes (just for information we have to
use !! instead of double pipes ;) that's why I always use concat and avoid
special characters in my codes.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von rob@xxxxxxxxx
Gesendet: Wednesday, 19. August 2009 15:59
An: Midrange Systems Technical Discussion
Betreff: Re: AW: Creating a dynamic view in SQL

A view over a view, interesting.
Not very index friendly but interesting.
And I take it you decided to leave the caution about not using || but
using CONCAT to the previous reply as to not beat a dead horse.

Rob Berendt

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].