Michael Shapiro writes:
> Thanks for this response. It still leave my question unanswered. I should
> rephrase it -- will become a native datatype in Postgres (as
> opposed to remaining an extension). Are there any plans to make a
> native datatype?
No. That is not the same as it being unsuppo
On Friday, June 12, 2015, Michael Shapiro wrote:
>
> The reason I am asking is that, although ltree seems to have been a
> contributed module since at least 8.3, how can one know if it will always
> be part of subsequent versions of Postgres?
>
Whether contrib, core, or an external extension you
On Friday, June 12, 2015, Michael Shapiro wrote:
> Hi Melvin,
>
> Thanks for this response. It still leave my question unanswered. I should
> rephrase it -- will become a native datatype in Postgres (as
> opposed to remaining an extension). Are there any plans to make a
> native datatype?
>
In
Hi Melvin,
Thanks for this response. It still leave my question unanswered. I should
rephrase it -- will become a native datatype in Postgres (as
opposed to remaining an extension). Are there any plans to make a
native datatype?
Michael
On Fri, Jun 12, 2015 at 7:58 AM, Melvin Davidson
wrote:
Geometric Data Types have been in PostgreSQL for quite a while.
http://www.postgresql.org/docs/9.2/interactive/datatype-geometric.html
JSON have been in PostgreSQL since 9.2 and it's functionality increases
with each new version.
http://www.postgresql.org/docs/9.2/interactive/datatype-json.html
A
I am wondering if the contributed module will always be part of
Postgres? Do contributed modules ever get absorbed into Postgres itself?
The reason I am asking is that, although ltree seems to have been a
contributed module since at least 8.3, how can one know if it will always
be part of subsequ
