-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thomas Kellerer wrote:
> Harald Armin Massa wrote on 13.08.2006 10:46:
>> Do you know for what benefit that happens? I have seen similiar stupidity
>> with EJB, having RI within that layer. Why are people doing this? Do they
>> know something I miss, or did they just not vivist Databases 101 ?
This is RDBMS Conventional Wisdom. Putting lots of logic into the
RDB has it's down-side though: depending on the RDBMS, you might
need an exclusive lock to modify a trigger or CHECK constraints,
drop a stored procedure, etc. If the object is on a popular table,
the whole app system may have to come down.
Next there's maintenance. A FK relationship may make on-line
archiving a parent-child table pair slower or more complicated than
if the FK relationship was managed by the app system.
Next, performance. If the server is burdened, or some of the RDBMS'
operations are inefficient, then doing the work inside the
application may be faster.
Lastly, there's politics. If the DBA/Operations team is in one
division, and the Development group is in another, the dev team
might want to keep much of the system knowledge to itself, and not
share with the DBAs.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE3vVTS9HxQb37XmcRAl3gAJ9ZxtE5zrhkgsXBgZ8J7YqdaIxPEgCfZ9qy
PBjxVm39dtz9crJkLrFti68=
=nKDU
-----END PGP SIGNATURE-----