Timeline for Rewriting query to match two points with linestring in different database table?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 7, 2014 at 11:16 | comment | added | simpleuser001 | ) was missing after ST_Equals and GROUB BY is GROUP BY.. query fixed , fails to non existing table on my machine so it should be ok | |
| Feb 7, 2014 at 11:14 | history | edited | simpleuser001 | CC BY-SA 3.0 |
fixed typpo
|
| Feb 7, 2014 at 10:27 | comment | added | fatbadger | Am using the SQL editor with PGAdmin by the way, seems I have to enclose all column names in double quotes - so like g."NODE_ID" etc. I've tried quoting EASTING and NORTHING in the LINESTRING function (like g."EASTING"), but to no avail. | |
| Feb 7, 2014 at 10:24 | comment | added | fatbadger | I've adapted your query to my DB (changed "gid" to "NODE_ID" and "linestrings" table is actually called "gps_node_links"). Am now getting a parse error at the start of the arguments to "'LINESTRING(g.EASTING g.NORTHING, -1.911782 53.26144)'". Any ideas why ? | |
| Feb 7, 2014 at 10:19 | comment | added | fatbadger | Many thanks, am trying it out now. Note the typo in "GROUP BY", and you need an extra closing bracket just before "GROUP". | |
| Feb 7, 2014 at 9:56 | history | answered | simpleuser001 | CC BY-SA 3.0 |