RE: looking for doc with diagrams on redo and undo for java developers (new title: Reuse of bad routines is worse than spaghetti code)

clearly I over reacted. I was thrown by the "major re-write" comment. Sounds like it was a major re-write to the one routine, which is actually a golden and good example of bundled code reuse.

mwf

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of ryan_gaffuri_at_comcast.net
Sent: Tuesday, September 28, 2004 2:05 PM To: Mark W. Farnham; oracle-l_at_freelists.org Subject: RE: looking for doc with diagrams on redo and undo for java developers (new title: Reuse of bad routines is worse than spaghetti code)

the mistake is perfectly understandable. reusable components can really speed up development time and ease maintenance. they just didn't know database architecture. method 4 dynamic sql stored in the database is the best way to go here... i think. these updates may run 250,000 times a day. i'll have to check to see how well dbms_sql works under that level of usage.

wasn't a fight. i found it in a code review. everyone was perfectly reasonable.
-------------- Original message --------------

> To the barracades, my friends!
>
> We must stamp out the notion that REUSE is a justification to populate the
> world with bad code.
>
> They want a reusable update handler? Fine. Write a good one and reuse it
at
> will. Better yet, have someone give you one that already works.
>
> Guns don't kill people.
> GO TOs don't create spaghetti code.
> Object handling principals and packages don't justify reuse and
propagation
> of bad code.
>
> Bad people can kill people a whole lot easier with guns than without guns.

--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l