Changes between Version 1 and Version 2 of DockerRdbmsTestEnvironment

Timestamp:

02/09/18 06:01:04 (7 years ago)

Author:

jng

Comment:

Added a note about some one-time setup required for PostgreSQL

DockerRdbmsTestEnvironment

@@ -26 +26 @@
 If your host OS is none of the above (eg. You are on Windows 7/8/8.1), you can use a virtual machine that is running one of the above OSes.
 
-= An example docker compose file =
+== An example docker compose file ==
 
 With the `docker-compose` tool that comes with a docker installation, you can spin up all the required databases to hit your RDBMS provider test suites against.
@@ -72 +72 @@
 On subsequent runs, the images are not downloaded (as they have been downloaded locally)
 
+== Some one-time PostgreSQL setup ==
+
+The PostgreSQL provider test suite assumes that `public` is the only schema of any PostGIS database it creates. The chosen docker image, while fully featured, breaks this assumption as it includes the `tiger` schema (for tiger geocoding), which the provider does not use, nor does the test suite exercise.
+
+So before running the PostgreSQL test suite, use a tool like pgAdmin to connect to the PostGIS docker container and make sure to drop any schema that is not `public` from the `template_postgis` and `postgres` databases.
+
+This action only needs to be done once.
+
+Alternatively, you could try a different PostGIS docker image (or roll your own) that does not include these extraneous schemas in their PostGIS database setup.
+
 == Running the GenericRdbms test suites against it ==