| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Best practices for aggregate table design |
| Date: | 2015-10-10 01:19:04 |
| Message-ID: | 56186788.80606@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/9/2015 6:07 PM, Roxanne Reid-Bennett wrote:
> On 10/9/2015 3:16 PM, droberts wrote:
>> Thanks for everyone's help. Can anyone recommend a good book on
>> database modeling, around these 'cube' or aggregate concepts in
>> particular? I'm using Postgres but shouldn't matter too much I assume.
>
> Given the shift towards NoSQL for BI, and the age of the consultants,
> I don't know how much of a driver of design patterns the Kimball Group
> still is in the BI/Data warehouse space - but their blogs and books
> have been good fodder for thought for the modeling I've done.
actually, there've been numerous cases where NoSQL deployments never
worked right, and people reverted to SQL for reporting.
--
john r pierce, recycling bits in santa cruz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Victor Blomqvist | 2015-10-10 03:30:21 | Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type: |
| Previous Message | Roxanne Reid-Bennett | 2015-10-10 01:07:22 | Re: Best practices for aggregate table design |