[postgis-devel] More dump comments

Obe, Regina robe.dnd at cityofboston.gov
Fri Feb 27 05:46:30 PST 2009


I guess no one knows the answer to the below 2 questions

In LWGeom_dump and LWGEOM_dump_rings

We do this

                /* allocate a slot for a tuple with this tupdesc */
                slot = TupleDescGetSlot(tupdesc);

                /* allocate a slot for a tuple with this tupdesc */
                slot = TupleDescGetSlot(tupdesc);

Is there a reason for setting this twice?

________________________________

From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Obe,
Regina
Sent: Wednesday, February 25, 2009 2:47 PM
To: PostGIS Development Discussion
Subject: [postgis-devel] More dump comments



Also according to this
http://doxygen.postgresql.org/execTuples_8c-source.html

It appears that TupleDescGetSlot is obsolete.  Does anyone know when it
became obsolete?

Interesting part of docs
/*
01050  * TupleDescGetSlot - Initialize a slot based on the supplied
tupledesc
01051  *
01052  * Note: this is obsolete; it is sufficient to call BlessTupleDesc
on
01053  * the tupdesc.  We keep it around just for backwards
compatibility with
01054  * existing user-written SRFs.
01055  */






________________________________

The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure pursuant
to Massachusetts law. It is intended solely for the addressee. If you
received this in error, please contact the sender and delete the
material from any computer. 

________________________________

Help make the earth a greener place. If at all possible resist printing
this email and join us in saving paper. 

-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.



More information about the postgis-devel mailing list