Changes between Version 38 and Version 39 of DevWikiGardenTest

Timestamp:

Dec 3, 2010, 5:30:24 AM (13 years ago)

Author:

robe

Comment:

—

DevWikiGardenTest

@@ -48 +48 @@
 }}}
 
-One nice benefit about logging the query and the output to a table, is that it's easier to inspect (and you can conceivably (thought haven't tried yet) do a join between two log output tables by logid to compare results from different versions of postgis) 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_3DDistance function that involve points and linestrings
+There are a lot of nice benefits  about logging the query and the output to a table:
+  * It's easier to inspect 
+  * You can conceivably (though haven't tried yet) do a join between two log output tables by logid (as long as the logs were generated from the same test script) to compare results from different versions of postgis) 
+  * 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_3DDistance function that involve points and linestrings
 
 {{{
@@ -59 +62 @@
 }}}
 
-You can even do even more cool things like use [http://developer.postgresql.org/pgdocs/postgres/pgbench.html pgbench] to simulate users with a transaction script that 
+ * You can even do even more cool things like use [http://developer.postgresql.org/pgdocs/postgres/pgbench.html pgbench] to simulate users with a transaction script that 
 looks something like the below script that will run 10 function queries on functions that
 start with ST_ that have succeeded in the past.
@@ -68 +71 @@
 END;
 }}}
+ * You can even run stats with the outputs as we are showing in our PL/R series [http://www.postgresonline.com/journal/archives/188-plr_part1.html Quick Intro to R and PL/R part 1]