[postgis-devel] Does changing deserialized data should change stored data?

[Pierre Racine]

Thanks,

I tried PG_DETOAST_DATUM_COPY and it fixes the problem however this does not explain why, when using PG_DETOAST_DATUM, sometimes the stored data is edited and sometimes it is not?

Pierre

>-----Original Message-----
>From: postgis-devel-bounces at postgis.refractions.net [mailto:postgis-devel-
>bounces at postgis.refractions.net] On Behalf Of strk
>Sent: 29 juillet 2010 13:26
>To: PostGIS Development Discussion
>Subject: Re: [postgis-devel] Does changing deserialized data should change stored data?
>
>On Wed, Jul 28, 2010 at 05:33:27PM -0400, Pierre Racine wrote:
>
>> Anybody have an idea why changing the deserialized data actually change the stored data?
>
>PG_DETOAST_DATUM copies or not based on size.
>PG_DETOAST_DATUM_COPY (or similar) forces the copy.
>
>--strk;
>
>  ()   Free GIS & Flash consultant/developer
>  /\   http://strk.keybit.net/services.html
>_______________________________________________
>postgis-devel mailing list
>postgis-devel at postgis.refractions.net
>http://postgis.refractions.net/mailman/listinfo/postgis-devel