| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Ways to deal with large amount of columns; |
| Date: | 2018-08-30 13:27:51 |
| Message-ID: | eea42068-5137-73d7-e86b-ab02f1b95bb8@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 30.08.2018 um 15:15 schrieb Robert Zenz:
> As David said, you'd be better off having a table that looks like this (in terms
> of columns):
>
> * MONTH
> * AGENT
> * CASHFLOW
>
> So your query to get the sum of a single agent would be looking like:
>
> select
> sum(CHASFLOW)
> where
> AGENT = 'Agent'
> and MONTH between values;
>
> It might be a little more work to create a GUI for that (or map this model to
> the existing GUI) but it is much simpler to maintain and work with.
agree. it is also possible to use partitioning.
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-08-30 13:48:26 | Re: pg_upgrade fails saying function unaccent(text) doesn't exist |
| Previous Message | Robert Zenz | 2018-08-30 13:15:07 | Re: Ways to deal with large amount of columns; |