Roman Podoliaka 98a6c1e4c4 postgresql: use postgres db instead of template1 ... In PostgreSQL template1 database is kind of special, as all new databases are copied from it, when you do CREATE DATABASE. This implies a few restrictions: e.g. you can't have more than one active session to template1, if one of them tries to create a database. It will fail with: ERROR: source database "template1" is being accessed by other users Using of postgres database instead of template1 resolves this issue. Closes-Bug: #1355929 Change-Id: I8b1a36163984fbef6be66964456072d32da6a9d0 (cherry picked from commit 02fa15b4ca)		2014-10-15 09:50:19 -07:00
..
__init__.py	Remove vi modelines	2014-02-03 14:19:44 +00:00
fakes.py	Remove vi modelines	2014-02-03 14:19:44 +00:00
test_db_api.py	Fix FloatingIP.save() passing FixedIP object to sqlalchemy	2014-08-07 23:48:15 -04:00
test_migration_utils.py	Fix sqlalchemy utils test cases for SA 0.9.x	2014-03-14 19:02:14 +02:00
test_migrations.conf	Fix tests to work with mysql+postgres concurrently	2013-10-27 09:46:45 +11:00
test_migrations.py	postgresql: use postgres db instead of template1	2014-10-15 09:50:19 -07:00
test_sqlalchemy_utils.py	Remove vi modelines	2014-02-03 14:19:44 +00:00
test_sqlite.py	Remove vi modelines	2014-02-03 14:19:44 +00:00