When you encounter a new application to build or enhance, do you automatically use OO? If not, what *do* you automatically use? You have to have *some* default, otherwise you do nothing.
No, I do not have a default. I look at the requirements and choose amongst
several tools, which for me includes RDBMSes, OO programming, and so on.
Bryce, I work at a place that is your wet dream. 1 million lines of procedural RDBMS code, using control tables, parms, and IF/THEN blocks. I have
direct experience with this. You have none. Yet you feel qualified to wave your hands and scream "tables are better!" when I have direct empirical evidence that they are not. There are 30 PL/SQL developers here who prefer to manage their configuration information in FILES. Every single one of them has TOAD on their computers and use it daily. They don't want the overhead, and they understand the issues. You do not, and you've got your fingers in your ears while I'm trying to demonstrate this to you. Perhaps on a small scale you may find them more convenient. Fine. I do not, these people do not, and your techniques simply do not scale. And quite frankly, if I have to draw my programmers from a pool that is mostly people who work on smaller apps, I'm going to look for people who know how to deal with files because
that's what works best at this scale. And all the hand-waving in the world won't change that.
Sure, if you get used to ANY primative tool, you will eventually learn to love the bomb.
Perhaps if I were working with a "primative" tools, I would. But I'm not. Given that there exist no tools for doing revisions of database tables, and there are for files, which is the primitive tool?
I did NOT say that. Commands are orthogonal to OO and files, BTW.
What you said was "How does tabling info preclude the use of a single command to initiate everything?" Which is not what you were asked. You were asked:
Hardly primitive. I can sit down with a blank system, type one command (bexvm build -d SID) and create an entire, running copy of our system, loaded config data, compiled code, everything. Unattended. This is primitive?
To which your response made no sense at all, so I reiterated. Answer the question: is that primitive, yes or no? No weaseling, no hand-waving. Answers other than yes or no will be ignored and the question posed again.
So does dealing with Flinstonian file systems.
Which you haven't shown. So far you've shown that using tables for config information requires more overhead.
No response, so concession noted.
Re: single command
