From: george young <gry@ll.mit.edu>
To: pgsql-sql@postgresql.org
Subject: Design Q.:logic in app or db?
Date: Wed, 26 Feb 2003 10:32:20 -0500
Message-ID: <20030226103220.6875cee9.gry@ll.mit.edu> (raw)
I have general design question about Postgres usage: How does one decide
how much, and what parts of logic should go in DB rules, triggers,
functions, constraints etc, versus what should go in the application?
I see postings here from people who obviously have a lot of domain
logic in the DB side. I currently have almost none. I plan to set up
a bunch of RI constraints to keep things clean and consistant, but what
about logic that implements frequent domain operations?
Brief sketch of my project: 2 developers, 4k lines of python(gtk, pygres),
2 main GUI user apps and a few read-only scripts for web display,
50 concurrent users(all local), DB performance important but not currently
a problem.
The main thing not done yet is to facilitate ad-hoc queries
(via odbc excel etc.) from db-naive users: maybe restructuring the
db to make it simpler, maybe views and functions... The data is
somewhat complex in structure.
-- George
--
I cannot think why the whole bed of the ocean is
not one solid mass of oysters, so prolific they seem. Ah,
I am wandering! Strange how the brain controls the brain!
-- Sherlock Holmes in "The Dying Detective"
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: gry@ll.mit.edu
Subject: Re: Design Q.:logic in app or db?
In-Reply-To: <20030226103220.6875cee9.gry@ll.mit.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox