Sunday, December 03, 2006

Reason 122,324,745...

Why server enforced integrity is relevant.

There are tons of reasons why placing integrity right next to the data (along with security and lots of other stuff) is important.  This article just tickled another one in my head.

Maybe, must maybe, someone will change your application.  It can be very easy - especially with "open standards" (common protocols).  This very simple article spells out at a very very high level things you need to think about.

Just go to google.com and type in SQL Injection sometime.  Read some of the articles there - think about what might happen.

POST A COMMENT

5 Comments:

Anonymous Sokrates said....

"server enforced integrity" - agree absolutely with you !

so hopefully Oracle will soon implement some improvements on this !

(number 1 on my wishlist:
that Oracle would give me the ability for a constraint "no overlaps" )

Mon Dec 04, 07:30:00 AM EST  

Anonymous Anonymous said....

The server enforced integrity article is blocked by my company's web nanny program because it's categorised as a 'sex' article. I know server enforced integrity is important, but sexy?!?!

Mon Dec 04, 07:57:00 AM EST  

Blogger Kim Berg Hansen said....

Good points from jpalmer - found one I have to implement. Thanks for showing this article, Tom.

(Except that he should update his methods on fixing SQL injection - he never mentioned bind variables :-)

Mon Dec 04, 10:14:00 AM EST  

Blogger Toon said....

I think he is talking about enforcing integrity on the 'application server'.
Not 'database server'.

Mon Dec 04, 03:29:00 PM EST  

Blogger SeanMacGC said....

I think he is talking about enforcing integrity on the 'application server'.
Not 'database server'


Why? (And 'server-side' is referred to, not 'database server'.)

Mon Dec 04, 04:14:00 PM EST  

POST A COMMENT

<< Home