pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedRe: Normalization is always good?
4+ messages / 3 participants
[nested] [flat]
* Re: Normalization is always good?
@ 2001-03-15 20:13 Josh Berkus <josh@agliodbs.com>
2001-03-15 23:28 ` Re: Normalization is always good? jkakar@expressus.com
0 siblings, 1 reply; 4+ messages in thread
From: Josh Berkus @ 2001-03-15 20:13 UTC (permalink / raw)
To: jkakar@expressus.com; +Cc: pgsql-sql
Jamu,
> I have been working with SQL databases for about a year in a half and
> in that time I've come to the conclusion that it is not always
> preferable to normalize to a high level (like 3rd level). In some
> cases, depending on the application, I've found that normalizing to a
> ridiculous degree has shot me in the foot in terms of the
> responsibility of my code to manage what happens in the database.
There I'd agree with you ... there is the question of *how rigorous* you
want your normalization to be. I tend to hover around the simplest
normal form, most of the time. And I do a few things (such as
polymorhic sub-tables) that would give Fabian Pascal fits :-)
However, there is (in my mind) no question as to whether a database
should be normalized, just how much effort is spent on normalization as
opposed to other considerations (UI, performance, development time).
> I've found referential integrity makes normalization a less expensive
> notion as it absolves you of the task of keeping data current in all
> your tables. I've also found that working in an object oriented
> language makes normalization less expensive.
What do you use? I've given up on OODB interfaces, myself, as I did not
find them helpful, but that's modtly because I was working in MS-land.
> What are the views of the people on this list re: Normalization
> Guidelines? Anybody know of any good web sites that talk about this
> in depth?
Yup. http://www.databasedebunking.com/ Dig through the archives.
-Josh Berkus
--
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Normalization is always good?
2001-03-15 20:13 Re: Normalization is always good? Josh Berkus <josh@agliodbs.com>
@ 2001-03-15 23:28 ` jkakar@expressus.com
2001-03-16 00:48 ` Re: Re: Normalization is always good? Christof Glaser <gcg@gl.aser.de>
2001-03-16 04:18 ` Re: Re: Normalization is always good? Josh Berkus <josh@agliodbs.com>
0 siblings, 2 replies; 4+ messages in thread
From: jkakar@expressus.com @ 2001-03-15 23:28 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-sql
Hi Josh,
> normal form, most of the time. And I do a few things (such as
> polymorhic sub-tables) that would give Fabian Pascal fits :-)
Polymorphic sub-tables? =) Do you mean using, for example, one user
table that stores different types of users and has some fields
specific to only some kinds of users and other fields that are shared
by all users?
> However, there is (in my mind) no question as to whether a database
> should be normalized, just how much effort is spent on normalization as
> opposed to other considerations (UI, performance, development time).
I agree. Anyone here familiar with "Extreme Programming"?- they
suggest that you should architect your software only for the
functionality you need NOW. While some aspects of extreme progrmming
have proven themselves true in the face of my skepticism I see it as
my moral obligation as programmer to write programs that are A) as
portable as possible and B) extensible. With that in mind, I like
normalization because it increases the likelihood of scalability being
relatively painless.
> What do you use? I've given up on OODB interfaces, myself, as I did not
> find them helpful, but that's modtly because I was working in MS-land.
I've been working in Java with JDBC... I've actually shot myself in
the foot a bit by not making my application object oriented enough.
In hindsight, and if time permitted more refactoring, I would have
written custom data objects to manage all interactions with the
database so that any management of data happened in one and only one
place and anything that needed to access those objects would do so
through the common interface.
> Yup. http://www.databasedebunking.com/ Dig through the archives.
Couldn't find the server... I wonder if it's still there.
Regards,
Jamu.
--
Jamu Kakar (Developer) Expressus Design Studio, Inc.
jkakar@expressus.com 708-1641 Lonsdale Avenue
V: (604) 903-6994 North Vancouver, BC, V7M 2J5
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Re: Normalization is always good?
2001-03-15 20:13 Re: Normalization is always good? Josh Berkus <josh@agliodbs.com>
2001-03-15 23:28 ` Re: Normalization is always good? jkakar@expressus.com
@ 2001-03-16 00:48 ` Christof Glaser <gcg@gl.aser.de>
1 sibling, 0 replies; 4+ messages in thread
From: Christof Glaser @ 2001-03-16 00:48 UTC (permalink / raw)
To: jkakar@expressus.com, Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-sql
On Friday, 16. March 2001 00:28, jkakar@expressus.com wrote:
>
> > Yup. http://www.databasedebunking.com/ Dig through the archives.
>
> Couldn't find the server... I wonder if it's still there.
Try this one: http://www.firstsql.com/dbdebunk/
Regards,
Christof
--
gl.aser . software engineering . internet service
http://gl.aser.de/ . Planckstraße 7 . D-39104 Magdeburg
Tel. +49.391.7 44 77 10 . Fax +49.391.7 44 77 13 . Mobil 0177.77 92 84 3
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Re: Normalization is always good?
2001-03-15 20:13 Re: Normalization is always good? Josh Berkus <josh@agliodbs.com>
2001-03-15 23:28 ` Re: Normalization is always good? jkakar@expressus.com
@ 2001-03-16 04:18 ` Josh Berkus <josh@agliodbs.com>
1 sibling, 0 replies; 4+ messages in thread
From: Josh Berkus @ 2001-03-16 04:18 UTC (permalink / raw)
To: jkakar@expressus.com, Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-sql
Jamu,
> Polymorphic sub-tables? =) Do you mean using, for example, one user
> table that stores different types of users and has some fields
> specific to only some kinds of users and other fields that are shared
> by all users?
Nope. What you described is a "not normalized" table. ;-)
One project contains a Notes table. However, I want it to be
configurable to what records notes apply ... that is, my application has
an admin option that allows you to configure the system so that there
are or aren't Notes for Client Addresses, for example.
TO do this, I created a sequence that is generally available
('universal_sq'), and set 7-9 tables to automatically increment a value
from the 'universal_sq' (column 'usq') for each record.
The Notes table, thus, effectively has the 'usq' as a foriegn key for 2
to 7 other tables, depending on user configuration. The wonderful
PostgreSQL sequence handler makes this possible. Thanks, Tom & team!
I've done this with a couple of other tables. Not relationally correct,
but I can't find anything wrong with the idea.
> Couldn't find the server... I wonder if it's still there.
I believe that Christof posted the correct URL.
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2001-03-16 04:18 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-03-15 20:13 Re: Normalization is always good? Josh Berkus <josh@agliodbs.com>
2001-03-15 23:28 ` jkakar@expressus.com
2001-03-16 00:48 ` Christof Glaser <gcg@gl.aser.de>
2001-03-16 04:18 ` Josh Berkus <josh@agliodbs.com>
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