Changes between Version 37 and Version 38 of DevWikiGardenTest
- Timestamp:
- 12/03/10 05:26:47 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevWikiGardenTest
v37 v38 12 12 == Version PostGIS 2.0+ == 13 13 The latest version includes logic that will during the tests - create two tables in the test database and populate them for later inspection: 14 * postgis_garden_log: This contains a record for each test and logs both the start, end times and the sql statement that was run.14 * '''postgis_garden_log''': This contains a record for each test and logs both the start, end times and the sql statement that was run. 15 15 columns are: logid- an autonumber, log_label - a short description, spatial_class - (will contain geometry or geography), func - name of function being tested, g1 - type of geometry of first geometry, g2 - type of geometry of second or null if a single geometry function, log_start - start time (timestamp), log_end - end time (timestamp), log_sql - the SQL statement that was run. 16 16 17 17 If the test crashes before completion, the record with the largest logid will tell you the query that crashed the server. 18 18 19 * postgis_garden_log_output-- this outputs the query results for queries that return something in xml format. It uses the built-in query_to_xml function that has existed since PostgreSQL 8.3 to do that.19 * '''postgis_garden_log_output''' -- this outputs the query results for queries that return something in xml format. It uses the built-in query_to_xml function that has existed since PostgreSQL 8.3 to do that. 20 20 columns: 21 21 * logid -- you can join this with the postgis_garden_log table to get the descriptive detail and SQL for the test.