From b301aa93948f05b5189382f641cf1e040fc655f2 Mon Sep 17 00:00:00 2001 From: Dimitri Fontaine Date: Fri, 16 Jun 2017 09:01:18 +0200 Subject: [PATCH] Review create-schemas default behavior. Get back in line with what the documentation says, and also fix the case for default MySQL migrations now that we target a PostgreSQL schema with the same name as the MySQL database name. Open question yet: should we also register the new schema on the search_path by default? ALTER DATABASE ... SET search_path TO public, newschema, ...; Is it more of a POLA violation to alter the search_path or to not do it? Fix #582. --- src/sources/common/db-methods.lisp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/sources/common/db-methods.lisp b/src/sources/common/db-methods.lisp index d72a664..36bf53c 100644 --- a/src/sources/common/db-methods.lisp +++ b/src/sources/common/db-methods.lisp @@ -213,7 +213,7 @@ (disable-triggers nil) (data-only nil) (schema-only nil) - (create-schemas nil) + (create-schemas t) (create-tables t) (include-drop t) (create-indexes t)