×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I reviewed that section of the Redbook. The author of that section on
database best practices makes several statements which are confusing and
misleading. The backdrop was a recommendation to pull only columns that you
need into a program as opposed to selecting all columns via Select *, which
is generally good advice.
That section does not address modular programming, which is suggested by
your question "one View per program"? No, different types of applications
will have different database requirements.
I bet you will find some use-cases for having "one View per program", and
other use-cases for having multiple views per program.
We use hundreds of SQL Views. They work great for applications. But we have
run into some administrative headaches when trying to restore Views which
have multiple-table dependencies from backup sources to libraries other
than the ones where the Views originated. We often end up restoring the
physical files - then regenerating the Views from SQL DDL Source.
Nathan.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
