all groups > sql server programming > september 2003 >
You're in the

sql server programming

group:

Check command


Re: Check command oj
9/9/2003 12:24:33 PM
sql server programming:
Both. Formatting is normally done at the client side. Data integrity is done
at backend side. This would ensure the most balance.

--
-oj
RAC v2.2 & QALite!
http://www.rac4sql.net


[quoted text, click to view]

Re: Check command Joe Celko
9/9/2003 1:44:34 PM
Neither :)

But the right answer is to put all of the business rules as possible in
the database.

That way you will have ONE AND ONLY ONE version of the rule. If you put
business logic in a front end applications, how do you assure that every
programmer in the future will code it the same way? That every host
language will compute it exactly the same way?

--CELKO--
===========================
Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, datatypes, etc. in your
schema are.

*** Sent via Developersdex http://www.developersdex.com ***
Check command Arjen
9/9/2003 9:18:44 PM
Hello,

When developing a software application with database access are the most
developers using the command check or are they checking values inside the
business logic?

Thanks!

Re: Check command Arjen
9/9/2003 10:46:35 PM
But are they using this command or are they just executing the SQL query.
When it goes wrong the catch it in the business logic?

Thanks!


"oj" <nospam_ojngo@home.com> schreef in bericht
news:OPhCBgwdDHA.3088@TK2MSFTNGP09.phx.gbl...
[quoted text, click to view]

AddThis Social Bookmark Button