Re: Databases as objects

Bob Badour wrote:
> DBMS_Plumber wrote:
>
>> Thomas Gagne wrote:
>>
>>> Bob, you're misunderstanding me.
>
> First, I understand Thomas just fine. As others here have noted, they
> understand him just fine too.
>
> Second, it makes little sense for Thomas to address me directly.
> Having noted Thomas' lack of intellectual honesty, I already added him
> to my killfile, and I will only see those things others reply to.
Bob, I stopped replying because you're rude. Others inside cdt manage to disagree without being rude. They're replies are easier to learn from.
> <snip>
> We understand you want to replace SQL with procedure calls as a proxy
> for object methods. How exactly is that not OOese?
???

I want to use procedure calls as a proxy for SQL, not object methods.

What I propose to do I can do without an OOPL. I can do without any programming language. I could do it using only SQL stored procedures inside an RDB. Sitting in front of my interactive SQL session instead of typing SQL for every business transaction I needed to repeatedly perform I would enter the name of a stored procedure(s). Programming languages add little to that except automation.

There's no OO programming involved. Zip. Zilch.
>
>
> I'm suggesting that the wonderful SQL you posted can be made
>>> into a DB-stored procedure to facilitate reuse,
>
> It was an ad hoc program. It was written to perform a single task one
> time. While one might need to perform a similar task in 12 month's
> time, the import schema will very likely change in the interim
> rendering the stored procedure useless. Whether one keeps the source
> code in the database or in some other repository, one will need to
> change it before using it again.
>
> Given that it only took a few moments to write, it will only take a
> few moments to write the appropriate program again when the time
> comes. In fact, trying to re-use the program may cause one to overlook
> subtle differences in next year's import schema, and I suggest it
> might be better to start from scratch.
I'm not thinking of operations performed once/year. I'm thinking of operations performed thousands of times every minute, or even thousands of times every day. You don't see value in creating a procedure for that?

-- 
Visit <http://blogs.instreamfinancial.com/anything.php> 
to read my rants on technology and the finance industry.