By bloid
via ckwop.me.uk
Published: Jul 13 2008 / 03:47
The vast majority of software that people write inside a business talks to a database. Yet object orientated programming does not gel well with databases. The code that looks clean and simple in a modern object orientated program looks positively terrible when you look at the traffic that code causes at the database.



Comments
miron.abramson replied ago:
Well written article!
dmitryx replied ago:
wtf? how programming paradigm affects db traffic?
if you have something against some ORM framework - name article "Is ORM-framework-N working?". What OOP has do to with it?
What a stupid idea!
Motion Control replied ago:
He writes "object orientated". He must be an expart.
antych replied ago:
Good example of someone not understanding OOP
herval replied ago:
I still don't get the "The writers of these packages are much like the inventor of this machine" comparison. Do they all look like psychos, is that it?
brixon replied ago:
One should be encouraged to Question Everything. Even things we hold to be self evident. There may be disagreements or even problems with the statement, but there may also be some truth hidden within.
I may not agree with 100% of what he wrote and I am not looking to discard OOP, but it does make you think how OOP and Databases differ and that the current approach with ORMs leave a lot to be desired.
http://en.wikipedia.org/wiki/Wikipedia:No_personal_attacks
adiand replied ago:
@brixon - IMHO There is an impedance mismatch because relational databases and OO programming address different concerns. OO is more than storage and representation of information. ORMs address the business of transferring information between Databases and Objects. They are lacking today, but this I suspect is more to do with the nascence of this technology and less with "impedance mismatch". Unfortunately in the business of Science innovation comes at a pace slower than we have become accustomed to :P
mknutty replied ago:
It seems, from looking at his bio, that his comments come from too little experience. Granted, people can learn a lot in a short period. Those of us who have done it "both" ways and multiple times realize which is the lesser of two evils. Granted, neither way is right every time and each side has its pros and cons. But over the long haul OOP wins out.
Kenneth Downs replied ago:
Extremely well written. I got OOP fever in the late 90's, wrote an ORM and immediately recognized it as a mistake. I abandoned it as a fool's errand and have never looked back. There is no impedance mismatch between OOP and Databases, there is an *interface* between two tiers that exist to serve different purposes. ORM is the impedance mismatch, because it connects them in a way that reduces the efficiency of both.
Voters For This Link (12)
Voters Against This Link (12)