On the topic of relational tables:
If I create a relational DB structure but do not define the relationship at
the database level, is there a loss in performance when my application
requests data from two tables based on the relationship. I guess what I'm
asking is do you need to define the relationship at the DB level?
Brook
At 06:00 PM 28/04/01 -0400, you wrote:
> > > as for normalizing; with a globally designed DB - it is not
> > > necessary; the logic is ported into the App.
> >
> > Well, sorry to bore people with this now slightly OT thread,
> > but "there's the rub" - by storing all the data in one table
> > you have thrown away all the inherent business-modelling
> > capability of a relational database and made far *more*
> > work for the developers, not less. Not only that,
> > but you lose the ability of the DB design to serve as
> > a central authoritative design document describing the
> > enterprise rules. Not to mention performance and the fact
> > that the database is now practically un-optimisable by the
> > DBMS and un-tunable by the DBA.
>
>This can't be repeated enough. There's a reason we all pay huge sums of
>money to Oracle, Sybase and so forth - relational databases work very well,
>if used correctly.
>
>Dave Watts, CTO, Fig Leaf Software
>http://www.figleaf.com/
>voice: (202) 797-5496
>fax: (202) 797-5444
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
