| From: | <markir(at)slingshot(dot)co(dot)nz> | 
|---|---|
| To: | <josh(at)agliodbs(dot)com>, Mark kirkwood <markir(at)slingshot(dot)co(dot)nz>, <pgsql-sql(at)postgresql(dot)org> | 
| Subject: | Re: How Postgresql Compares For Some Query Types | 
| Date: | 2001-07-18 23:02:12 | 
| Message-ID: | 200107182302.f6IN2Ha23201@postgresql.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-sql | 
> 
> 	I'm a little unclear on what a "fact table" is.  Can you explain?
Good question... The idea comes from data warehousing where a typical data 
construction involves two "types" of table :
dimensions : time, location, ethicity....( essentially denormalized lookups )
facts      : observations, accidents, sales ....
facts have a composite primary key , each componant of which is a foreign key 
for one of the dimensions.
If drawn with the fact table(s) in the center and dimensions around about, then 
the ERD looks like a "star". Hence the names "star schema" and "star query"
A quick search located a vaguely helpful page : ( apologies about the source )
http://www.oradoc.com/ora816/server.816/a76994/schemas.htm
A much better source is Kimball's book "The Data Warehousing Toolkit".
regards
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2001-07-18 23:53:32 | Re: pl/pgsql - code review + question | 
| Previous Message | Tom Lane | 2001-07-18 20:34:58 | Re: pl/pgsql - code review + question |