Timeline for Getting "missing FROM-clause" error when adding ST_Intersects constraint to PostGIS table
Current License: CC BY-SA 4.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 9, 2019 at 22:33 | comment | added | geozelot |
well, there is no 'simpler' way, and compared to triggers (that do offer plenty more options) often used, the elegancy of this did make me happy when I read about custom funcs in constraints. the EXISTS is special in that it stops execution as soon as it encounters the first 1/true, SELECT 1 scans the whole filtered range of rows. you can add a REGCLASS parameter to refer a relation (e.g. table) with inherent catalog/search path checks and thus security (although others types are possible). the && is a bounding box comparator, used here to limit actual ST_Intersection operations.
|
|
| May 9, 2019 at 20:17 | history | answered | user19425 | CC BY-SA 4.0 |