| From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
|---|---|
| To: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
| Cc: | Derek Poon <derekp+pgsql(at)ece(dot)ubc(dot)ca>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Hierarchical numeric data type |
| Date: | 2013-08-07 10:21:02 |
| Message-ID: | CAKt_ZfundccbWMWwXssD8VnVy_DsboJMdVkWxFmzR8CWdYjq6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
This depends on exactly what you need. In the end usually you are going to
want to convert things into integer arrays.
In LedgerSMB we use integers and foreign keys to handle hierarchies, and
then convert them to int arrays via WITH RECURSIVE CTE's and text strings .
This is one of those things where hierarchical data design can depend
heavily on the use case.
--
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
lock-in.
http://www.efficito.com/learn_more.shtml
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sameer Thakur | 2013-08-07 10:34:01 | Populating array of composite datatype |
| Previous Message | Vishalakshi Navaneethakrishnan | 2013-08-07 09:46:54 | How to avoid Force Autovacuum |