This discussion is around the database software industry since
the beggining of time.

If you want, let's say, use your software in a multitude of
databases - so put only the data integrity rules on the DB,
the rest on the UI.

If you need to access the data within other applications,
put as many rules possible on the DB.

Multiplataform UIs certainly will opt for BR in RBDMS, since
is only one implementation of them and is acessible to all
platforms supported.

In other words: if you do mix, use only on UI or only in DB;
is just a matter of satisfying your needs.

On Wed, 22 Feb 2006 06:46:14 -0000, mlq97 wrote:

>What is the perceived wisdom about where to put business rules for a
>simple app? (Into the database or the front end?)
>
>I'm planning a commercial Win32 (Firebird) database application which
>will mainly be used as a single user standalone program, with a small
>percentage of users using a networked workgroup version, so this is
>unlikely to ever need 3 tier architecture.
>
>Is it better to put maximum "intelligence" into the DB in the form of
>referential rules, sql procedures and triggers etc, or should this be
>mainly in the (Delphi)front end?
>
>I'm concerned about:
>
>1. Protection of the intellectual property.
>2. Ease of design & maintenance.
>
>Thanks in advance for any guidance.
>
>
>
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Visit http://firebird.sourceforge.net and click the Resources item
>on the main (top) menu. Try Knowledgebase and FAQ links !
>
>Also search the knowledgebases at http://www.ibphoenix.com
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Yahoo! Groups Links
>
>
>
>
>
>
>