Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Matt Penning — — source: Usenet: comp.databases.informix
Two view-related feature requests:
1) don't require the column list in view creation
i.e. "create view foo as select myfunc() as mycol" ought to work,
instead of having to write "create view foo (mycol) as select myfunc()
as mycol". If you are telling IDS what the column is via "as mycol", why
have to also list that column?
2) optimize ansi joins in views
currently optimizer required IDS style joins to do optimization - would
like to see this expanded to handle standard ansi syntax
- Matt
I;m adding both.
1. Less likely to be implemented since it is not that hard to
wordaround.
and once you have the view definition setup how often do you change it/
add new views.
2. Yes! I would have thought that the process is
a) parse sql and built internal form of parse tree
b) read internal parse tree and optimize query
I would have thought that in the internal form of the parse tree is the
same
for ANSI sql and Informix sql queries that have the same meaning
would be the same but I guess not!
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.