20 | | columns: logid -- you can join this with the postgis_garden_log table to get the descriptive detail and SQL for the test. log_out - an xml field that contains the query_to_xml output of the query. |
| 20 | columns: |
| 21 | * logid -- you can join this with the postgis_garden_log table to get the descriptive detail and SQL for the test. |
| 22 | * log_output - an xml field that contains the query_to_xml output of the query. |
| 23 | |
| 24 | The really nice benefit about logging the query and the output to a table, is that it's easier to inspect and you can also rerun a subset of the queries for closer inspection by just writing an sql statement something like below -- which will test all tests for the ST_Distance function that involve points and linestrings |
| 25 | |
| 26 | {{{ |
| 27 | SELECT logid, log_label, query_to_xml(log_sql, false,false,'') As result, log_sql |
| 28 | FROM postgis_garden_log |
| 29 | WHERE func = 'ST_3DDistance' AND |
| 30 | (g1 IN('POINTZ', 'MULTIPOINTZ', 'LINESTRINGZ') OR |
| 31 | g2 IN('POINTZ', 'MULTIPOINTZ', 'LINESTRINGZ') ) |
| 32 | ) ; |
| 33 | }}} |
| 34 | |