Re: OO vs. RDB challenge
From: frebe (fredrik_bertilsson_at_passagen.se)
Date: 03/20/05
- Next message: frebe: "Re: Application logic and Business logic"
- Previous message: Jeff Brooks: "Re: Application logic and Business logic"
- In reply to: alex99_at_medcentral.com.au: "Re: OO vs. RDB challenge"
- Next in thread: alex99_at_medcentral.com.au: "Re: OO vs. RDB challenge"
- Reply: alex99_at_medcentral.com.au: "Re: OO vs. RDB challenge"
- Reply: Alfredo Novoa: "Re: OO vs. RDB challenge"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 20 Mar 2005 10:48:01 -0800
> That example was about 10 years
Maybe RDBMS technology has improved in ten years. I think you should
avoid giving performance statistics that are 10 years old.
> > The thing is database optimizers, indexes and joins can easily be
> > beaten if you think about things.
> We did it routinely.
Then you would have no problem reproduce such example and sent it to
me.
>> That is because you don't know what a database is. If your team had
>> some developers that knew something about databases, he would let
you
>> touch it.
> Now now Fredrick, how can you make that statement about me you don't
> even know who I am. You don't know what knowledge I have about
> databases.
I only know what you have shown in this debate....
> Nor do you know the dba's and the corporate policy (which is to ban
> programmers from touching production systems without exception).
We are not debating your company's policy here. I am talking about how
a DBA in general should work.
>>There are a standard named ANSI SQL. All major database
>> vendors supports a very large subset of this standard.
> Really, that's news to me. Everytime I use SQL I get bitten by vendor
> specifics.
I have recently converted a large enterprise application originally
written for Informix, to support Oracle and SQL Server as well. 99,99%
of the SQL statements are identical for all dialects.
> If accounts only expose limited ports and MQ or a Corba object
happens
> to be running on that port what can you do?
Stop using an DBMS is not the answer anyway.
> Your idea of good software engineering is too late for those guys.
What
> do we do now?
A bad design will always give you problems. If your company uses the
DBMS in a bad way and major changes is not longer possible, you need to
do what it takes to make it work. But don't use that experience as an
argument for not using a DBMS in new applications. Try to see what
mistakes they did, and make sure they (or someone else) don't do it
again.
Fredrik Bertilsson
http://butler.sourceforge.net
- Next message: frebe: "Re: Application logic and Business logic"
- Previous message: Jeff Brooks: "Re: Application logic and Business logic"
- In reply to: alex99_at_medcentral.com.au: "Re: OO vs. RDB challenge"
- Next in thread: alex99_at_medcentral.com.au: "Re: OO vs. RDB challenge"
- Reply: alex99_at_medcentral.com.au: "Re: OO vs. RDB challenge"
- Reply: Alfredo Novoa: "Re: OO vs. RDB challenge"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|