From: Tobias Brox <tobias@nordicbet.com>
To: Chad Wagner <chad.wagner@gmail.com>
Cc: Tobias Brox <tobias@nordicbet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: extract(field from timestamp) vs date dimension
Date: Tue, 23 Jan 2007 14:35:48 +0100
Message-ID: <20070123133548.GA17420@oppetid.no> (raw)
In-Reply-To: <81961ff50701230524y14aa883alfe4dab8d1dd5cf10@mail.gmail.com>
References: <20070123124937.GA13122@oppetid.no>
<81961ff50701230524y14aa883alfe4dab8d1dd5cf10@mail.gmail.com>
[Chad Wagner - Tue at 08:24:34AM -0500]
> I guess go with your gut, but at some point the expressions are going to be
> too complicated to maintain, and inefficient.
The layout of my system is quite flexible, so it should eventually be
fairly trivial to throw in a date dimension at a later stage.
> Calendar tables are very very common, because traditional date functions
> simply can't define business logic (especially things like month end close,
> quarter end close, and year end close) that doesn't have any repeating
> patterns (every 4th friday, 1st monday in the quarter, etc). Sure you can
> stuff it into a function, but it just isn't as maintainable as a table.
So far I haven't been bothered with anything more complex than "clean"
weeks, months, quarters, etc.
I suppose the strongest argument for introducing date dimensions already
now is that I probably will benefit from having conform and
well-designed dimensions when I will be introducing more data marts. As
for now I have only one fact table and some few dimensions in the
system.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tobias@nordicbet.com, chad.wagner@gmail.com
Subject: Re: extract(field from timestamp) vs date dimension
In-Reply-To: <20070123133548.GA17420@oppetid.no>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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