The other issue with the cycle is that is File I/O based. I write 100%
SQL unless I absolutely have to use File I/O because of an abnormal
database.
The question is always the same. How often do you need to bring in just
one thing to a program? 99% of the time you need multiple things brought
in together and that is what SQL shines at and I am bringing into the
program only what I need and I have database independence.
My only question is why people continue to use file I/O. Again guys in
my shop will write dozens of lines of insanely complex logic to chain in
data and read it instead of one simple SQL statement. Makes no sense to
me.
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
