Timeline for Assign order number in which line intersect polygons
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 12, 2016 at 9:46 | history | suggested | Matt | CC BY-SA 3.0 |
improved wording
|
| Oct 12, 2016 at 9:19 | review | Suggested edits | |||
| S Oct 12, 2016 at 9:46 | |||||
| Jun 24, 2016 at 5:39 | vote | accept | Miro | ||
| Jun 24, 2016 at 5:17 | comment | added | Pierma | With my small data test, both are instant. It is the final part of the query who is very long for big dataset. This part create the position indexes. What about use the python plugin ArMoraer create for you here :gis.stackexchange.com/questions/192048/… | |
| Jun 24, 2016 at 3:32 | comment | added | Miro | Thank you. I did that before - I replaced both r "FROM r AS b" and "FROM r AS a" by the part in WITH clause and it worked well. Though the performance of that query is very very slow. I was wondering if with "WITH" the performance is better... | |
| Jun 24, 2016 at 3:26 | comment | added | Pierma | It works fine for me. You can rewrite the query without WITH (WITH is just for clarification) : in "FROM r AS b" and in "FROM r AS a", replace "r" by the code inside the WITH statment (with parenthesis). | |
| Jun 24, 2016 at 3:12 | comment | added | Miro | I can't make it work even with most simple statement like "WITH test AS (SELECT * FROM pg) SELECT * FROM test". The rest of query works as expected. | |
| Jun 24, 2016 at 2:59 | comment | added | Pierma | WITH should works. The debugging information on error messages are not very helpfull because the position of the error is not given. He tell you "near WIDH" because it's the first line. The error can be everywhere inside the with statement. Post your modified query and I will look. | |
| Jun 24, 2016 at 2:25 | comment | added | Miro | I can't make WITH clause working at all in Create Virtual Layer Query. Always writes syntax error near "WITH". Any hint? | |
| Jun 21, 2016 at 3:51 | comment | added | Miro | Thank you, I though virtual layer might be at help here. Seems switching from long term QGIS 2.8 to 2.14 is inevitable :) | |
| Jun 21, 2016 at 3:40 | history | answered | Pierma | CC BY-SA 3.0 |