Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org