what's a better code design priciple?

[rcgraves at brandeis.edu (Rich Graves)]

Principles? I've heard of those.

If you're writing a serious application for a real RDBMS (Oracle or
PostgreSQL), it's worth your time to put the business logic in stored
procedures and make your front ends more declarative than procedural.

However that tends to lock you into a particular database forever.

If you're using MySQL, you simply don't have that choice. You have to put
all the logic in your application. You also don't need to worry about the
overhead of multiple queries because it's so damn fast. Beware of locking,
consistency, and backup issues, though.

Here's an entertaining introduction to the topic.

http://photo.net/sql/your-own-rdbms.html
-- 
Rich Graves <rcgraves at brandeis.edu>
UNet Systems Administrator

Please don't talk to me about Windows 2000. If you did, it might become illegal
for me to support it. http://www.salon.com/tech/log/2000/05/11/slashdot_censor/

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