On Fri, Apr 11, 2008 at 9:02 PM, Tom Lane <[EMAIL PROTECTED]> wrote: > To be blunt, that seems like a really bad idea, and I have not the > slightest hesitation about breaking your ability to do it. How > do you know that the recheck-need corresponds to what you are testing > on the application side?
>From what I read when I did that a few months ago, the recheck was added to provide SRID checking. If you don't have it, you don't have the SRID mismatch error when SRIDs don't match. > If there's actually some safe, consistent use for such behavior > then I think you need to lobby the PostGIS project to provide > access to it. In the general case, there isn't. If you enforce the SRID (using a wrapper/constraints/whatever), there is. After some googling, I finally found the post of Mark Cave-Ayland on postgis-users which made me take this decision: http://www.mail-archive.com/[EMAIL PROTECTED]/msg01206.html Don't know if there is a better way to do it in PostGIS itself but the ability to take this decision for a specific database (or even column) is really convenient. -- Guillaume -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
