QGIS/tests/testdata/provider/testdata_pg.sh

#!/bin/sh

SCRIPTS="
  tests/testdata/provider/testdata_pg.sql
  tests/testdata/provider/testdata_pg_reltests.sql
  tests/testdata/provider/testdata_pg_vectorjoin.sql
  tests/testdata/provider/testdata_pg_hstore.sql
"

dropdb qgis_test 2> /dev/null || true
createdb qgis_test || exit 1
for f in ${SCRIPTS}; do
  psql -f $f qgis_test --set ON_ERROR_STOP=1 || exit 1
done
Add script to create and initialize postgis test database 2016-02-17 11:08:18 +01:00			`#!/bin/sh`

			`SCRIPTS="`
			`tests/testdata/provider/testdata_pg.sql`
			`tests/testdata/provider/testdata_pg_reltests.sql`
			`tests/testdata/provider/testdata_pg_vectorjoin.sql`
Add hstore support to the postgres provider 2016-08-26 14:43:59 +02:00			`tests/testdata/provider/testdata_pg_hstore.sql`
Add script to create and initialize postgis test database 2016-02-17 11:08:18 +01:00			`"`

Smarter default edit widgets with plugins to pick them Now the widgets factories can give a score on how good they could handle a widget. Additionaly, plugins can be added to choose a widget factory in function of an external information. One of them uses a table in PostgresQL to allow specification of the widget type and configuration. I took the opportunity to remove a few deprecated method in relation to this. 2016-07-15 12:11:43 +02:00			`dropdb qgis_test 2> /dev/null \|\| true`
Add script to create and initialize postgis test database 2016-02-17 11:08:18 +01:00			`createdb qgis_test \|\| exit 1`
			`for f in ${SCRIPTS}; do`
			`psql -f $f qgis_test --set ON_ERROR_STOP=1 \|\| exit 1`
			`done`