On 02/05/2012 02:31 PM, Stefan Keller wrote:
Hi Andrew
Nice work!
Just for completeness: Did you also think of including geometry types
in JSON output functions in later releases? There's a nice extension
of JSON called GeoJSON for a starting point.
[side note: please don't top-reply on -h
Hi Andrew
Nice work!
Just for completeness: Did you also think of including geometry types
in JSON output functions in later releases? There's a nice extension
of JSON called GeoJSON for a starting point.
Yours, Stefan
2012/2/3 Andrew Dunstan :
>
>
> On 02/02/2012 12:20 PM, Pavel Stehule wrote
On 02/02/2012 12:20 PM, Pavel Stehule wrote:
2012/2/2 Andrew Dunstan:
On 02/02/2012 04:35 AM, Abhijit Menon-Sen wrote:
At 2012-02-01 18:48:28 -0500, andrew.duns...@pgexperts.com wrote:
For now I'm inclined not to proceed with that, and leave it as an
optimization to be considered later if n
2012/2/2 Andrew Dunstan :
>
>
> On 02/02/2012 04:35 AM, Abhijit Menon-Sen wrote:
>>
>> At 2012-02-01 18:48:28 -0500, andrew.duns...@pgexperts.com wrote:
>>>
>>> For now I'm inclined not to proceed with that, and leave it as an
>>> optimization to be considered later if necessary. Thoughts?
>>
>> I
On 02/02/2012 04:35 AM, Abhijit Menon-Sen wrote:
At 2012-02-01 18:48:28 -0500, andrew.duns...@pgexperts.com wrote:
For now I'm inclined not to proceed with that, and leave it as an
optimization to be considered later if necessary. Thoughts?
I agree, there doesn't seem to be a pressing need to
At 2012-02-01 18:48:28 -0500, andrew.duns...@pgexperts.com wrote:
>
> For now I'm inclined not to proceed with that, and leave it as an
> optimization to be considered later if necessary. Thoughts?
I agree, there doesn't seem to be a pressing need to do it now.
-- ams
--
Sent via pgsql-hackers
