implementing the rules of business within the database

#1

Guys!

is it better to implement the business logic within the database? i.e.
through functions, triggers, constraints .. etc

or implement the logic within the application?

does implementing the logic within the db violates the MVC principle?

#2

Mahdi <ce (AT) mail (DOT) net.sk> wrote:

Quote:

is it better to implement the business logic within the database? i.e.
through functions, triggers, constraints .. etc

or implement the logic within the application?

Depends. If you want to be database independant, implement the logic in
a model layer in the app. If you are sure, you'll always stay with the
database, but can't say so for the application layer, implement as much
as you can in the database.

Quote:

does implementing the logic within the db violates the MVC principle?

Don't think so. As long as you keep everything inside a model / storage
layer, you should be fine.

I have my datamodel with all the integrity constraints and so on in the
database, everything else in a model layer in my application
(WebObjects).

cug

--
http://www.event-s.net

#3

Mahdi <ce (AT) mail (DOT) net.sk> wrote:

Quote:

is it better to implement the business logic within the database? i.e.
through functions, triggers, constraints .. etc

or implement the logic within the application?

Depends. If you want to be database independant, implement the logic in
a model layer in the app. If you are sure, you'll always stay with the
database, but can't say so for the application layer, implement as much
as you can in the database.

Quote:

does implementing the logic within the db violates the MVC principle?

Don't think so. As long as you keep everything inside a model / storage
layer, you should be fine.

I have my datamodel with all the integrity constraints and so on in the
database, everything else in a model layer in my application
(WebObjects).

cug

--
http://www.event-s.net

#4

Mahdi <ce (AT) mail (DOT) net.sk> wrote:

Quote:

is it better to implement the business logic within the database? i.e.
through functions, triggers, constraints .. etc

or implement the logic within the application?

Depends. If you want to be database independant, implement the logic in
a model layer in the app. If you are sure, you'll always stay with the
database, but can't say so for the application layer, implement as much
as you can in the database.

Quote:

does implementing the logic within the db violates the MVC principle?

Don't think so. As long as you keep everything inside a model / storage
layer, you should be fine.

I have my datamodel with all the integrity constraints and so on in the
database, everything else in a model layer in my application
(WebObjects).

cug

--
http://www.event-s.net

#5

Mahdi <ce (AT) mail (DOT) net.sk> wrote:

Quote:

is it better to implement the business logic within the database? i.e.
through functions, triggers, constraints .. etc

or implement the logic within the application?

Depends. If you want to be database independant, implement the logic in
a model layer in the app. If you are sure, you'll always stay with the
database, but can't say so for the application layer, implement as much
as you can in the database.

Quote:

does implementing the logic within the db violates the MVC principle?

Don't think so. As long as you keep everything inside a model / storage
layer, you should be fine.

I have my datamodel with all the integrity constraints and so on in the
database, everything else in a model layer in my application
(WebObjects).

cug

--
http://www.event-s.net

#6

Mahdi <ce (AT) mail (DOT) net.sk> wrote:

Quote:

is it better to implement the business logic within the database? i.e.
through functions, triggers, constraints .. etc

or implement the logic within the application?

Depends. If you want to be database independant, implement the logic in
a model layer in the app. If you are sure, you'll always stay with the
database, but can't say so for the application layer, implement as much
as you can in the database.

Quote:

does implementing the logic within the db violates the MVC principle?

Don't think so. As long as you keep everything inside a model / storage
layer, you should be fine.

I have my datamodel with all the integrity constraints and so on in the
database, everything else in a model layer in my application
(WebObjects).

cug

--
http://www.event-s.net

#7

Mahdi <ce (AT) mail (DOT) net.sk> wrote:

Quote:

is it better to implement the business logic within the database? i.e.
through functions, triggers, constraints .. etc

or implement the logic within the application?

Depends. If you want to be database independant, implement the logic in
a model layer in the app. If you are sure, you'll always stay with the
database, but can't say so for the application layer, implement as much
as you can in the database.

Quote:

does implementing the logic within the db violates the MVC principle?

Don't think so. As long as you keep everything inside a model / storage
layer, you should be fine.

I have my datamodel with all the integrity constraints and so on in the
database, everything else in a model layer in my application
(WebObjects).

cug

--
http://www.event-s.net

#8

Mahdi <ce (AT) mail (DOT) net.sk> wrote:

Quote:

is it better to implement the business logic within the database? i.e.
through functions, triggers, constraints .. etc

or implement the logic within the application?

Depends. If you want to be database independant, implement the logic in
a model layer in the app. If you are sure, you'll always stay with the
database, but can't say so for the application layer, implement as much
as you can in the database.

Quote:

does implementing the logic within the db violates the MVC principle?

Don't think so. As long as you keep everything inside a model / storage
layer, you should be fine.

I have my datamodel with all the integrity constraints and so on in the
database, everything else in a model layer in my application
(WebObjects).

cug

--
http://www.event-s.net

#9

Mahdi <ce (AT) mail (DOT) net.sk> wrote:

Quote:

is it better to implement the business logic within the database? i.e.
through functions, triggers, constraints .. etc

or implement the logic within the application?

Depends. If you want to be database independant, implement the logic in
a model layer in the app. If you are sure, you'll always stay with the
database, but can't say so for the application layer, implement as much
as you can in the database.

Quote:

does implementing the logic within the db violates the MVC principle?

Don't think so. As long as you keep everything inside a model / storage
layer, you should be fine.

I have my datamodel with all the integrity constraints and so on in the
database, everything else in a model layer in my application
(WebObjects).

cug

--
http://www.event-s.net

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

implementing the rules of business within the database

comp.databases.postgresql comp.databases.postgresql

implementing the rules of business within the database - 08-14-2008 , 08:50 PM

Re: implementing the rules of business within the database - 08-14-2008 , 10:46 PM

Re: implementing the rules of business within the database - 08-14-2008 , 10:46 PM

Re: implementing the rules of business within the database - 08-14-2008 , 10:46 PM

Re: implementing the rules of business within the database - 08-14-2008 , 10:46 PM

Re: implementing the rules of business within the database - 08-14-2008 , 10:46 PM

Re: implementing the rules of business within the database - 08-14-2008 , 10:46 PM

Re: implementing the rules of business within the database - 08-14-2008 , 10:46 PM

Re: implementing the rules of business within the database - 08-14-2008 , 10:46 PM