September 10th, 2002, 12:48 AM
|
|
Contributing User
|
|
Join Date: May 2001
Location: New Zealand
Posts: 638
Time spent in forums: 22 m 10 sec
Reputation Power: 8
|
|
This is the classic thread - many laughs, I like it 
Quote: | Many younger programmers like to put these constraints into the application code, but I believe that is almost always a mistake, because now your database itself will not maintain those constraints if other applications connect to it, not to mention that it is far more risky to depend on application code, rather than internal DB integrity. |
I really have to make a small comment about this quote, because it *soooo* applies to myself. I thought that it would be fun to do everything in PHP, and using mysql was the perfect way to teach me how to. Then I got together with a certain DBA, and suddenly I started getting a hammering about what a real database is  Lol
If you want a reallly scalable app, that is secure, move your business logic into the database. It is (1) faster and (2) more secure, and I guarantee that it what your clients want. We're not going to use MySQL again, no disrespect intended, but we need stored procedures, views, integrity constraints to build scalable web services, or so our DBA tells me
Awesome, Z.
|
Dev Shed Forums Sponsor:
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
