Re: "Business Logic / Rules should never be in the database or stored procedures"
From: Gerard H. Pille <ghp_at_skynet.be>
Date: Mon, 14 Dec 2009 22:14:46 +0100
Message-ID: <4b26aac3$0$2848$ba620e4c_at_news.skynet.be>
Tim X wrote:
>
> Some good points and reminds me of something else I forgot to mention.
> something I've often seen in applications that have the business rules
> in the applicaiton layer and none in the database (i.e. basic CRUD) is
> much much larger data retrievals/transfers. These systems tend to do
> little filtering of the data at the db level. instead, they retrieve
> large chunks of data and then filter it at the app level and then curse
> Oracle for being inefficient! It stuns me that people think something
> like Java sorting and filtering out data will be more efficient than
> doing it at the SQL level.
>
> Tim
>
Date: Mon, 14 Dec 2009 22:14:46 +0100
Message-ID: <4b26aac3$0$2848$ba620e4c_at_news.skynet.be>
Tim X wrote:
>
> Some good points and reminds me of something else I forgot to mention.
> something I've often seen in applications that have the business rules
> in the applicaiton layer and none in the database (i.e. basic CRUD) is
> much much larger data retrievals/transfers. These systems tend to do
> little filtering of the data at the db level. instead, they retrieve
> large chunks of data and then filter it at the app level and then curse
> Oracle for being inefficient! It stuns me that people think something
> like Java sorting and filtering out data will be more efficient than
> doing it at the SQL level.
>
> Tim
>
Precious few people care about this. Received on Mon Dec 14 2009 - 15:14:46 CST