| From: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
|---|---|
| To: | Misa Simic <misa(dot)simic(at)gmail(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Graph datatype addition |
| Date: | 2013-04-30 08:52:01 |
| Message-ID: | CAOeZVif3Ri9jnWUh2KAeh613SUsvTaVbtsG7HKj6G9sUa48_Fw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Have you considered maybe ltree datatype?
>
> To me all described sounds solveable on pure sql way ( + ltree datatype to
> help with indexes and performance as materialised path to avoid recursive
> query all the time...)
This may build over the existing solutions itself. I will have to check that.
> Though would be nice to see something new what would simplify the tasks...
Exactly.A specialized data type with built in support for common
operations will be helpful,IMHO.
Regards,
Atri
--
Regards,
Atri
l'apprenant
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atri Sharma | 2013-04-30 08:59:13 | Re: Graph datatype addition |
| Previous Message | Dimitri Fontaine | 2013-04-30 08:50:26 | Re: [HACKERS] pgsql: Add sql_drop event for event triggers |