> 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.
I worked on a client-server project exactly 10 years ago
where the database designer tried the same approach.
It didn't work. Obviously times have changed but..
the upside needs to be pretty good to outweigh all that.
Nick
**********************************************************************
Information in this email is confidential and may be privileged.
It is intended for the addressee only. If you have received it in error,
please notify the sender immediately and delete it from your system.
You should not otherwise copy it, retransmit it or use or disclose its
contents to anyone.
Thank you for your co-operation.
**********************************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
