Brent Wood wrote:
Ashish Karalkar wrote:
Thanks Brent for your replay,
What about the Disadvantages, Performance issues?
As far as I'm aware, performance is the only real disadvantage.
What performance are we talking about here? Executing from a view
although has *some* overhead, I don't even know that it is worth
considering in most cases.
Joshua D. Drake
I tend to break DB design into stages:
ER modelling to define the entities/relationships the DB needs to
store/represent
Normalize this to maximise data integrity & minimise duplication/redundancy
De-normalise to meet performance & access requirements.
In the latter stage, views are generally used, unless there are
performance restrictions,
when a de-normalised schema may be applied.
Cheers,
Brent
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
