what's a better code design priciple?

[Jesse Noller]

Typically, with SQL, I keep multiple smaller queries, sectioning out the
work, thatway, i can cache queries where possible, and then turn around and
keep my code eaily maintainable. "modulizing" my code seems to be the
defacto way to keeping it easier to read and maintain.

Just my .000002 cents.

-Jesse

> -----Original Message-----
> From: Christoph Doerbeck A242369 [mailto:cdoerbec at cso.fmr.com]
> Sent: Tuesday, May 30, 2000 2:17 PM
> To: discuss at Blu.Org
> Subject: what's a better code design priciple?
> 
> 
> 
> Hey folks,
> 
> I am at a cross roads in the development of a little application.
> What's better in the interest of performance and (more 
> importantly) code
> maintainability?
> 
> 	a) use multiple simple SQL queries requiring additional code 
> 	b) increase SQL complexibilty, use one query and reduce 
> code size
> 
> Comments?  Obviously it's tough to gauge the best solution 
> without knowing
> my design in detail, but I was wondering if there were some hacker
> standards I should go by...
> 
> 
> 
> - Christoph
> 
> 
> -
> Subcription/unsubscription/info requests: send e-mail with
> "subscribe", "unsubscribe", or "info" on the first line of the
> message body to discuss-request at blu.org (Subject line is ignored).
> 
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).