[postgis-users] Strange problem with && Problem worked around

[Paragon Corporation]

More updates.  Okay the ST_DropBBOx and ST_AddBBox putting in my triggers
did not remedy the situation.  I was however (at least I think I have),
isolated the issue to a before trigger I was using.  I moved this trigger
from being a before to being an after and that seemed to resolve the issue.

Does this mean I can't have before triggers that update geometry fields
because it will always interfere with PostGIS cachebox trigger or am I just
doing something stupid.

Thanks,
Regina
 

-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Paragon
Corporation
Sent: Thursday, November 06, 2008 11:56 PM
To: 'PostGIS Users Discussion'
Subject: RE: [postgis-users] Strange problem with && Problem worked around

I guess I should add to this.  It just occurred to me that maybe my trigger
is getting in the way of PostGIS's ability to add and drop the bounding
boxes and so maybe what I was seeing were cached boxes before the move.

So I dropped my triggers and then ran the below and that seemed to make the
table answer agree with my static answer and be what I was expecting. 

UPDATE ga.ga_other_edges
SET the_geom = ST_DropBBOX(the_geom)
WHERE tlid IN(66664219,66664276);


UPDATE ga.ga_other_edges
SET the_geom = ST_AddBBOX(the_geom)
WHERE tlid IN(66664219,66664276);


So I guess the work around is to add the ST_DropBBOX, ST_AddBBOX as part of
my trigger.  Can any one think of a better solution to this problem.  

Any other thoughts would be appreciated.

Thanks,
Regina


_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users