Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: Thomas Gagne <tgagne@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 26 Jan 2007 13:44:12 -0500
frebe73@xxxxxxxxx wrote:
<snip>Can you give an example of an application that would have an excessive number of getemployeBySomeCriteria() methods that doesn't encroach on becoming a report writer? All our reports have been implemented as stored procedures and have been meticulously crafted to perform well and balance to other reports. There are many similarly-named reports but the user doesn't really see that because they navigate through the data starting at the top-level and drilling-down.
No, of course I would use the database to fetch the data I want. I'd
make sure that a well structure SQL statement was used against a
well-normalized database. Who wouldn't?
You claim that it is possible to only have a few number of
getEmployeeBySomeCriteria methods with optimized SQL statements for
every different way you might need to fetch employee data? That should
only be possible for rather small applications.
If there really was a requirement for ad-hoc getEmployee() methods than an ad-hoc or report-writing tool is needed--and that's a different kind of application than a business application like accounting, mortgages, finance, statements, etc... don't you think?
Plentiful. Didn't we discuss this in "Databases as objects?" The biggest difference between Martin's and my approaches in this area is my belief the system starts with the data model and his starts with an behavioral model. Mind you, that's not a trivial difference...Then I would hide that SQL statement behind an interface so that the
rest of my application was unaware of it.
And the benifits are?
--
Visit <http://blogs.instreamfinancial.com/anything.php> to read my rants on technology and the finance industry.
.
- Follow-Ups:
- References:
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: JXStern
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: topmind
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: Robert Martin
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: topmind
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: Robert Martin
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: frebe73
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: Robert Martin
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: frebe73
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: Robert Martin
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: frebe73
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- Prev by Date: Use Case problem
- Next by Date: Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- Previous by thread: Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- Next by thread: Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- Index(es):
Relevant Pages
|