blocks|key|301630|text|在django/db/backends/creation.py中修改以下方法|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|301631|def+_destroy_test_db(self,+test_database_name,+verbosity):
++++"Internal+implementation+-+remove+the+test+db+tables."

++++#+Remove+the+test+database+to+clean+up+after
++++#+ourselves.+Connect+to+the+previous+database+(not+the+test+database)
++++#+to+do+so,+because+it's+not+allowed+to+delete+a+database+while+being
++++#+connected+to+it.
++++self._set_test_dict()
++++cursor+=+self.connection.cursor()
++++self.set_autocommit()
++++time.sleep(1)+#+To+avoid+"database+is+being+accessed+by+other+users"+errors.

++++cursor.execute("""SELECT+table_name+FROM+information_schema.tables+WHERE+table_schema='public'""")
++++rows+=+cursor.fetchall()
++++for+row+in+rows:
++++++++try:
++++++++++++print+"Dropping+table+'%25s'"+%25+row[0]
++++++++++++cursor.execute('drop+table+%25s+cascade+'+%25+row[0])
++++++++except:
++++++++++++print+"Couldn't+drop+'%25s'"+%25+row[0]+

++++#cursor.execute("DROP+DATABASE+%25s"+%25+self.connection.ops.quote_name(test_database_name))
++++self.connection.close()

def+_create_test_db(self,+verbosity,+autoclobber):
++++"Internal+implementation+-+creates+the+test+db+tables."

++++suffix+=+self.sql_table_creation_suffix()

++++if+self.connection.settings_dict['TEST_NAME']:
++++++++test_database_name+=+self.connection.settings_dict['TEST_NAME']
++++else:
++++++++test_database_name+=+TEST_DATABASE_PREFIX+%2B+self.connection.settings_dict['NAME']

++++qn+=+self.connection.ops.quote_name

++++#+Create+the+test+database+and+connect+to+it.+We+need+to+autocommit
++++#+if+the+database+supports+it+because+PostgreSQL+doesn't+allow
++++#+CREATE/DROP+DATABASE+statements+within+transactions.
++++self._set_test_dict()
++++cursor+=+self.connection.cursor()
++++self.set_autocommit()

++++return+test_database_name

def+_set_test_dict(self):
++++if+"TEST_NAME"+in+self.connection.settings_dict:
++++++++self.connection.settings_dict["NAME"]+=+self.connection.settings_dict["TEST_NAME"]
++++if+"TEST_USER"+in+self.connection.settings_dict:
++++++++self.connection.settings_dict['USER']+=+self.connection.settings_dict["TEST_USER"]
++++if+"TEST_PASSWORD"+in+self.connection.settings_dict:
++++++++self.connection.settings_dict['PASSWORD']+=+self.connection.settings_dict["TEST_PASSWORD"]|code-block|syntax|javascript|301632|看起来很有效。如果需要，只需将额外的设置添加到settings.py中即可。|301633|entityMap^0|1|U|0|0|N|B|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Modify the following methods in <code>django/db/backends/creation.py</code>:

<pre class="lang-python prettyprint-override"><code>def _destroy_test_db(self, test_database_name, verbosity):
 "Internal implementation - remove the test db tables."

 # Remove the test database to clean up after
 # ourselves. Connect to the previous database (not the test database)
 # to do so, because it's not allowed to delete a database while being
 # connected to it.
 self._set_test_dict()
 cursor = self.connection.cursor()
 self.set_autocommit()
 time.sleep(1) # To avoid "database is being accessed by other users" errors.

 cursor.execute("""SELECT table_name FROM information_schema.tables WHERE table_schema='public'""")
 rows = cursor.fetchall()
 for row in rows:
 try:
 print "Dropping table '%s'" % row[0]
 cursor.execute('drop table %s cascade ' % row[0])
 except:
 print "Couldn't drop '%s'" % row[0] 

 #cursor.execute("DROP DATABASE %s" % self.connection.ops.quote_name(test_database_name))
 self.connection.close()

def _create_test_db(self, verbosity, autoclobber):
 "Internal implementation - creates the test db tables."

 suffix = self.sql_table_creation_suffix()

 if self.connection.settings_dict['TEST_NAME']:
 test_database_name = self.connection.settings_dict['TEST_NAME']
 else:
 test_database_name = TEST_DATABASE_PREFIX + self.connection.settings_dict['NAME']

 qn = self.connection.ops.quote_name

 # Create the test database and connect to it. We need to autocommit
 # if the database supports it because PostgreSQL doesn't allow
 # CREATE/DROP DATABASE statements within transactions.
 self._set_test_dict()
 cursor = self.connection.cursor()
 self.set_autocommit()

 return test_database_name

def _set_test_dict(self):
 if "TEST_NAME" in self.connection.settings_dict:
 self.connection.settings_dict["NAME"] = self.connection.settings_dict["TEST_NAME"]
 if "TEST_USER" in self.connection.settings_dict:
 self.connection.settings_dict['USER'] = self.connection.settings_dict["TEST_USER"]
 if "TEST_PASSWORD" in self.connection.settings_dict:
 self.connection.settings_dict['PASSWORD'] = self.connection.settings_dict["TEST_PASSWORD"]
</code></pre>

Seems to work... just add the extra settings to your <code>settings.py</code> if you need 'em.

blocks|key|299353|text|我认为更好的解决方案可能是define+your+own+test+runner。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|299354|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/stable/topics/testing/advanced/#defining-a-test-runner^0|D|R|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I think a better solution might be to <a href="https://docs.djangoproject.com/en/stable/topics/testing/advanced/#defining-a-test-runner" rel="nofollow noreferrer">define your own test runner</a>.

blocks|key|3245839|text|我也遇到过类似的问题。但我想让Django绕过为我的一个实例创建测试数据库(这不是一个很难的镜像)。按照Mark的建议，我创建了一个自定义的测试运行程序，如下所示|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3245840|from+django.test.simple+import+DjangoTestSuiteRunner


class+ByPassableDBDjangoTestSuiteRunner(DjangoTestSuiteRunner):

++++def+setup_databases(self,+**kwargs):
++++++++from+django.db+import+connections
++++++++old_names+=+[]
++++++++mirrors+=+[]

++++++++for+alias+in+connections:
++++++++++++connection+=+connections[alias]
++++++++++++#+If+the+database+is+a+test+mirror,+redirect+its+connection
++++++++++++#+instead+of+creating+a+test+database.
++++++++++++if+connection.settings_dict['TEST_MIRROR']:
++++++++++++++++mirrors.append((alias,+connection))
++++++++++++++++mirror_alias+=+connection.settings_dict['TEST_MIRROR']
++++++++++++++++connections._connections[alias]+=+connections[mirror_alias]
++++++++++++elif+connection.settings_dict.get('BYPASS_CREATION','no')+==+'no':
++++++++++++++++old_names.append((connection,+connection.settings_dict['NAME']))
++++++++++++++++connection.creation.create_test_db(self.verbosity,+autoclobber=not+self.interactive)
++++++++return+old_names,+mirrors|code-block|syntax|javascript|3245841|然后，我在settings.py、'BYPASS_CREATION':'yes',中的一个数据库条目中创建了一个额外的字典条目|offset|length|style|CODE|3245842|最后，我用配置了一个新的TestRunner|3245843|TEST_RUNNER+=+'auth.data.runner.ByPassableDBDjangoTestSuiteRunner'|3245844|entityMap^0|0|0|H|O|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I had a similar issue. But I wanted Django to just bypass the creation of a test database for one of my instances (it is not a mirror tough). Following Mark's suggestion, I created a custom test runner, as follows

<pre><code>from django.test.simple import DjangoTestSuiteRunner


class ByPassableDBDjangoTestSuiteRunner(DjangoTestSuiteRunner):

 def setup_databases(self, **kwargs):
 from django.db import connections
 old_names = []
 mirrors = []

 for alias in connections:
 connection = connections[alias]
 # If the database is a test mirror, redirect its connection
 # instead of creating a test database.
 if connection.settings_dict['TEST_MIRROR']:
 mirrors.append((alias, connection))
 mirror_alias = connection.settings_dict['TEST_MIRROR']
 connections._connections[alias] = connections[mirror_alias]
 elif connection.settings_dict.get('BYPASS_CREATION','no') == 'no':
 old_names.append((connection, connection.settings_dict['NAME']))
 connection.creation.create_test_db(self.verbosity, autoclobber=not self.interactive)
 return old_names, mirrors
</code></pre>

Then I created an extra dict entry in one of my databases entries inside settings.py, <code>'BYPASS_CREATION':'yes',</code>

Finally, I configured a new TestRunner with

<pre><code>TEST_RUNNER = 'auth.data.runner.ByPassableDBDjangoTestSuiteRunner'
</code></pre>

blocks|key|3245871|text|你可以使用django-nose作为你的TEST_RUNNER。安装后，如果您传递以下环境变量，它将不会删除并重新创建数据库(首先自己手动创建)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3245872|REUSE_DB=1+./manage.py+test|code-block|syntax|javascript|3245873|您还可以将以下代码添加到settings.py中，这样就不必在每次运行测试时都编写REUSE_DB=1：|3245874|os.environ['REUSE_DB']+=+"1"|3245875|注意：这也会让你所有的表都留在数据库中，这意味着测试设置会更快一点，但是当你改变你的模型时，你将不得不手动更新表(或者自己删除并重新创建数据库)。|style|BOLD|3245876|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jbalogh/django-nose^0|5|B|0|0|0|0|0|0|3|10|K|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|14|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|15|8|@$A|16|B|17|O|P]|$A|18|B|19|O|P]]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

You could use <a href="https://github.com/jbalogh/django-nose" rel="nofollow">django-nose</a> as your TEST_RUNNER. Once installed, if you pass the following environment variable, it will not delete and re-create the database (create it manually yourself first).

<pre><code>REUSE_DB=1 ./manage.py test
</code></pre>

You can also add the following to settings.py so you don't have to write REUSE_DB=1 every time you want to run tests:

<pre><code>os.environ['REUSE_DB'] = "1"
</code></pre>

Note: this will also leave all your tables in the databases which means test setup will be a little quicker, but you will have to manually update the tables (or delete and re-create the database yourself) when you change your models.

blocks|key|299369|text|我建议将sqlite3用于测试目的，同时继续使用mysql/postgres/等用于生产。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|299370|这可以通过在您的设置文件中放置以下内容来实现：|299371|if+'test'+in+sys.argv:
++++DATABASES['default']+=+{'ENGINE':+'django.db.backends.sqlite3'}|code-block|syntax|javascript|299372|请参阅Running+django+tests+with+sqlite|offset|length|299373|将在您的django项目主目录中创建一个临时sqlite数据库文件，您可以对其进行写访问。另一个优点是sqlite3的测试速度要快得多。但是，如果您正在使用任何mysql/postgres特定的原始sql+(无论如何都应该尽量避免)，您可能会遇到问题。|299374|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/6353124/running-django-tests-with-sqlite^0|0|0|0|3|W|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@$K|10|L|11|1|12]]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

I would suggest using sqlite3 for testing purposes while keeping on using mysql/postgres/etc for production.

This can be achieved by placing this in your settings file:

<pre><code>if 'test' in sys.argv:
 DATABASES['default'] = {'ENGINE': 'django.db.backends.sqlite3'}
</code></pre>

see <a href="https://stackoverflow.com/questions/6353124/running-django-tests-with-sqlite">Running django tests with sqlite</a>

a temporary sqlite database file will be created in your django project home which you will have write access to. The other advantage is that sqlite3 is much faster for testing. You may however run in to problems if you are using any mysql/postgres specific raw sql (which you should try to avoid anyway).

blocks|key|3245905|text|我的数据库重用变体：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3245906|from+django.test.simple+import+DjangoTestSuiteRunner
from+django.core.management+import+call_command


class+TestRunner(DjangoTestSuiteRunner):
++++def+setup_databases(self,+**kwargs):
++++++++from+django.db+import+connections

++++++++settings+=+connections['default'].settings_dict
++++++++settings['NAME']+=+settings['TEST_NAME']
++++++++settings['USER']+=+settings['TEST_USER']
++++++++settings['PASSWORD']+=+settings['TEST_PASSWD']

++++++++call_command('syncdb',+verbosity=1,+interactive=False,+load_initial_data=False)

++++def+teardown_databases(self,+old_config,+**kwargs):
++++++++from+django.db+import+connection

++++++++cursor+=+connection.cursor()
++++++++cursor.execute('show+tables;')
++++++++parts+=+('DROP+TABLE+IF+EXISTS+%25s;'+%25+table+for+(table,)+in+cursor.fetchall())
++++++++sql+=+'SET+FOREIGN_KEY_CHECKS+=+0;\n'+%2B+'\n'.join(parts)+%2B+'SET+FOREIGN_KEY_CHECKS+=+1;\n'
++++++++connection.cursor().execute(sql)|code-block|syntax|javascript|3245907|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

my variant to reusing database:

<pre><code>from django.test.simple import DjangoTestSuiteRunner
from django.core.management import call_command


class TestRunner(DjangoTestSuiteRunner):
 def setup_databases(self, **kwargs):
 from django.db import connections

 settings = connections['default'].settings_dict
 settings['NAME'] = settings['TEST_NAME']
 settings['USER'] = settings['TEST_USER']
 settings['PASSWORD'] = settings['TEST_PASSWD']

 call_command('syncdb', verbosity=1, interactive=False, load_initial_data=False)

 def teardown_databases(self, old_config, **kwargs):
 from django.db import connection

 cursor = connection.cursor()
 cursor.execute('show tables;')
 parts = ('DROP TABLE IF EXISTS %s;' % table for (table,) in cursor.fetchall())
 sql = 'SET FOREIGN_KEY_CHECKS = 0;\n' + '\n'.join(parts) + 'SET FOREIGN_KEY_CHECKS = 1;\n'
 connection.cursor().execute(sql)
</code></pre>

blocks|key|3031852|text|我在上面的评论中添加了这一点，但它有点迷失了--最近对网络功能的改变让这件事变得更容易。现在可以创建new+private+database+instances了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3031853|按照那里的说明操作，在创建新用户时，请确保授予他们访问ALTER+USER+new_username+CREATEDB;的权限。|style|CODE|3031854|您可能还应该更改默认的cron设置，这样他们就不会尝试检查此数据库是否已启动并频繁运行。|3031855|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.webfaction.com/software/private-databases.html#creating-private-postgresql-databases-and-users^0|1E|U|0|0|R|X|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@$A|W|B|X|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

I added this to the comments above but it got kind of lost - recent changes to webfaction make this MUCH easier. You can now create <a href="http://docs.webfaction.com/software/private-databases.html#creating-private-postgresql-databases-and-users" rel="nofollow">new private database instances</a>. 

Follow the instructions there, and when creating a new user make sure to give them the permission to <code>ALTER USER new_username CREATEDB;</code>.

You probably also should change the default cron settings so they don't try to check if this database is up and runnings as frequently.

blocks|key|3031896|text|下面是一个使用Webfaction+XML-RPC+API创建数据库的django测试套件运行器。请注意，使用API设置数据库可能需要长达一分钟的时间，并且脚本可能会暂时停滞，请稍等片刻。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3031897|注意:控制面板密码存在安全风险，因为有人入侵您的web服务器SSH可能会接管您的web帐户。如果这是一个问题，请将USE_SESSKEY设置为True，并使用此脚本下面的fabric脚本将会话id传递给服务器。上一次API调用的会话密钥expires+in+1+hour。|3031898|文件测试:在服务器中，您需要配置./manage.py+test_runner.py才能使用WebfactionTestRunner|3031899|"""
This+test+runner+uses+Webfaction+XML-RPC+API+to+create+and+destroy+database
"""

#+you+can+put+your+control+panel+username+and+password+here.
#+NOTE:+there+is+a+security+risk+of+having+control+panel+password+in
#+the+webfaction+server,+because+someone+breaching+into+your+web+server
#+SSH+could+take+over+your+Webfaction+account.+If+that+is+a+concern,
#+set+USE_SESSKEY+to+True+and+use+the+fabric+script+below+this+script+to
#+generate+a+session.

USE_SESSKEY+=+True
#+CP_USERNAME+=+'webfactionusername'+#+required+if+and+only+if+USE_SESSKEY+is+False
#+CP_PASSWORD+=+'webfactionpassword'+#+required+if+and+only+if+USE_SESSKEY+is+False

import+sys
import+os
from+django.test.simple+import+DjangoTestSuiteRunner
from+django+import+db
from+webfaction+import+Webfaction

def+get_sesskey():
++++f+=+os.path.expanduser("~/sesskey")
++++sesskey+=+open(f).read().strip()
++++os.remove(f)
++++return+sesskey

if+USE_SESSKEY:
++++wf+=+Webfaction(get_sesskey())
else:
++++wf+=+Webfaction()
++++wf.login(CP_USERNAME,+CP_PASSWORD)


def+get_db_user_and_type(connection):
++++db_types+=+{
++++++++'django.db.backends.postgresql_psycopg2':+'postgresql',
++++++++'django.db.backends.mysql':+'mysql',
++++}
++++return+(
++++++++connection.settings_dict['USER'],
++++++++db_types[connection.settings_dict['ENGINE']],
++++)


def+_create_test_db(self,+verbosity,+autoclobber):
++++"""
++++Internal+implementation+-+creates+the+test+db+tables.
++++"""

++++test_database_name+=+self._get_test_db_name()

++++db_user,+db_type+=+get_db_user_and_type(self.connection)

++++try:
++++++++wf.create_db(db_user,+test_database_name,+db_type)
++++except+Exception+as+e:
++++++++sys.stderr.write(
++++++++++++"Got+an+error+creating+the+test+database:+%25s\n"+%25+e)
++++++++if+not+autoclobber:
++++++++++++confirm+=+raw_input(
++++++++++++++++"Type+'yes'+if+you+would+like+to+try+deleting+the+test+"
++++++++++++++++"database+'%25s',+or+'no'+to+cancel:+"+%25+test_database_name)
++++++++if+autoclobber+or+confirm+==+'yes':
++++++++++++try:
++++++++++++++++if+verbosity+>=+1:
++++++++++++++++++++print("Destroying+old+test+database+'%25s'..."
++++++++++++++++++++++++%25+self.connection.alias)
++++++++++++++++wf.delete_db(test_database_name,+db_type)
++++++++++++++++wf.create_db(db_user,+test_database_name,+db_type)
++++++++++++except+Exception+as+e:
++++++++++++++++sys.stderr.write(
++++++++++++++++++++"Got+an+error+recreating+the+test+database:+%25s\n"+%25+e)
++++++++++++++++sys.exit(2)
++++++++else:
++++++++++++print("Tests+cancelled.")
++++++++++++sys.exit(1)

++++db.close_connection()
++++return+test_database_name


def+_destroy_test_db(self,+test_database_name,+verbosity):
++++"""
++++Internal+implementation+-+remove+the+test+db+tables.
++++"""
++++db_user,+db_type+=+get_db_user_and_type(self.connection)
++++wf.delete_db(test_database_name,+db_type)
++++self.connection.close()


class+WebfactionTestRunner(DjangoTestSuiteRunner):
++++def+__init__(self,+*args,+**kwargs):
++++++++#+Monkey+patch+BaseDatabaseCreation+with+our+own+version
++++++++from+django.db.backends.creation+import+BaseDatabaseCreation
++++++++BaseDatabaseCreation._create_test_db+=+_create_test_db
++++++++BaseDatabaseCreation._destroy_test_db+=+_destroy_test_db

++++++++return+super(WebfactionTestRunner,+self).__init__(*args,+**kwargs)|code-block|syntax|javascript|3031900|文件webfaction.py:这是一个fabfile.py的瘦包装器，它需要可以被test_runner.py+(在远程服务器中)和fabfile.py(在本地机器中)导入。|3031901|import+xmlrpclib

class+Webfaction(object):
++++def+__init__(self,+sesskey=None):
++++++++self.connection+=+xmlrpclib.ServerProxy("https://api.webfaction.com/")
++++++++self.sesskey+=+sesskey

++++def+login(self,+username,+password):
++++++++self.sesskey,+_+=+self.connection.login(username,+password)

++++def+create_db(self,+db_user,+db_name,+db_type):
++++++++"""+Create+a+database+owned+by+db_user+"""
++++++++self.connection.create_db(self.sesskey,+db_name,+db_type,+'unused')

++++++++#+deletes+the+default+user+created+by+Webfaction+API
++++++++self.connection.make_user_owner_of_db(self.sesskey,+db_user,+db_name,+db_type)
++++++++self.connection.delete_db_user(self.sesskey,+db_name,+db_type)

++++def+delete_db(self,+db_name,+db_type):
++++++++try:
++++++++++++self.connection.delete_db_user(self.sesskey,+db_name,+db_type)
++++++++except+xmlrpclib.Fault+as+e:
++++++++++++print+'ignored+error:',+e
++++++++try:
++++++++++++self.connection.delete_db(self.sesskey,+db_name,+db_type)
++++++++except+xmlrpclib.Fault+as+e:
++++++++++++print+'ignored+error:',+e|3031902|文件fabfile.py:生成会话密钥的示例fabric脚本，仅在USE_SESSKEY=True时才需要|3031903|from+fabric.api+import+*
from+fabric.operations+import+run,+put
from+webfaction+import+Webfaction
import+io

env.hosts+=+["webfactionusername@webfactionusername.webfactional.com"]
env.password+=+"webfactionpassword"

def+run_test():
++++wf+=+Webfaction()
++++wf.login(env.hosts[0].split('@')[0],+env.password)
++++sesskey_file+=+'~/sesskey'
++++sesskey+=+wf.sesskey
++++try:
++++++++put(io.StringIO(unicode(sesskey)),+sesskey_file,+mode='0600')
++++++++#+put+your+test+code+here
++++++++#+e.g.+run('DJANGO_SETTINGS_MODULE=settings+/path/to/virtualenv/python+/path/to/manage.py+test+--testrunner=test_runner.WebfactionTestRunner')
++++++++raise+Exception('write+your+test+here')
++++finally:
++++++++run("rm+-f+%25s"+%25+sesskey_file)|3031904|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.webfaction.com/xmlrpc-api/apiref.html|1|http://community.webfaction.com/questions/11859/api-session_id-expiration^0|7|M|0|0|3A|H|1|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|F|3|G|5|6|7|1C|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1D|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1E|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1F|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1G|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1H|8|@]|9|@]|C|$K|L]]|$1|U|3|-4|5|6|7|1I|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]|12|$5|X|Y|Z|C|$10|13]]]]

The following is a django test suite runner to create database using <a href="https://docs.webfaction.com/xmlrpc-api/apiref.html" rel="nofollow">Webfaction XML-RPC API</a>. Note, setting up the database using the API may take up to a minute, and the script may appear to be stuck momentarily, just wait for a little while.

NOTE: there is a security risk of having control panel password in the webfaction server, because someone breaching into your web server SSH could take over your Webfaction account. If that is a concern, set USE_SESSKEY to True and use the fabric script below this script to pass a session id to the server. The session key <a href="http://community.webfaction.com/questions/11859/api-session_id-expiration" rel="nofollow">expires in 1 hour</a> from the last API call.

File test_runner.py: in the server, you need to configure ./manage.py test to use WebfactionTestRunner

<pre><code>"""
This test runner uses Webfaction XML-RPC API to create and destroy database
"""

# you can put your control panel username and password here.
# NOTE: there is a security risk of having control panel password in
# the webfaction server, because someone breaching into your web server
# SSH could take over your Webfaction account. If that is a concern,
# set USE_SESSKEY to True and use the fabric script below this script to
# generate a session.

USE_SESSKEY = True
# CP_USERNAME = 'webfactionusername' # required if and only if USE_SESSKEY is False
# CP_PASSWORD = 'webfactionpassword' # required if and only if USE_SESSKEY is False

import sys
import os
from django.test.simple import DjangoTestSuiteRunner
from django import db
from webfaction import Webfaction

def get_sesskey():
 f = os.path.expanduser("~/sesskey")
 sesskey = open(f).read().strip()
 os.remove(f)
 return sesskey

if USE_SESSKEY:
 wf = Webfaction(get_sesskey())
else:
 wf = Webfaction()
 wf.login(CP_USERNAME, CP_PASSWORD)


def get_db_user_and_type(connection):
 db_types = {
 'django.db.backends.postgresql_psycopg2': 'postgresql',
 'django.db.backends.mysql': 'mysql',
 }
 return (
 connection.settings_dict['USER'],
 db_types[connection.settings_dict['ENGINE']],
 )


def _create_test_db(self, verbosity, autoclobber):
 """
 Internal implementation - creates the test db tables.
 """

 test_database_name = self._get_test_db_name()

 db_user, db_type = get_db_user_and_type(self.connection)

 try:
 wf.create_db(db_user, test_database_name, db_type)
 except Exception as e:
 sys.stderr.write(
 "Got an error creating the test database: %s\n" % e)
 if not autoclobber:
 confirm = raw_input(
 "Type 'yes' if you would like to try deleting the test "
 "database '%s', or 'no' to cancel: " % test_database_name)
 if autoclobber or confirm == 'yes':
 try:
 if verbosity &gt;= 1:
 print("Destroying old test database '%s'..."
 % self.connection.alias)
 wf.delete_db(test_database_name, db_type)
 wf.create_db(db_user, test_database_name, db_type)
 except Exception as e:
 sys.stderr.write(
 "Got an error recreating the test database: %s\n" % e)
 sys.exit(2)
 else:
 print("Tests cancelled.")
 sys.exit(1)

 db.close_connection()
 return test_database_name


def _destroy_test_db(self, test_database_name, verbosity):
 """
 Internal implementation - remove the test db tables.
 """
 db_user, db_type = get_db_user_and_type(self.connection)
 wf.delete_db(test_database_name, db_type)
 self.connection.close()


class WebfactionTestRunner(DjangoTestSuiteRunner):
 def __init__(self, *args, **kwargs):
 # Monkey patch BaseDatabaseCreation with our own version
 from django.db.backends.creation import BaseDatabaseCreation
 BaseDatabaseCreation._create_test_db = _create_test_db
 BaseDatabaseCreation._destroy_test_db = _destroy_test_db

 return super(WebfactionTestRunner, self).__init__(*args, **kwargs)
</code></pre>

File webfaction.py: this is a thin wrapper for Webfaction API, it need to be importable by both test_runner.py (in the remote server) and the fabfile.py (in the local machine)

<pre><code>import xmlrpclib

class Webfaction(object):
 def __init__(self, sesskey=None):
 self.connection = xmlrpclib.ServerProxy("https://api.webfaction.com/")
 self.sesskey = sesskey

 def login(self, username, password):
 self.sesskey, _ = self.connection.login(username, password)

 def create_db(self, db_user, db_name, db_type):
 """ Create a database owned by db_user """
 self.connection.create_db(self.sesskey, db_name, db_type, 'unused')

 # deletes the default user created by Webfaction API
 self.connection.make_user_owner_of_db(self.sesskey, db_user, db_name, db_type)
 self.connection.delete_db_user(self.sesskey, db_name, db_type)

 def delete_db(self, db_name, db_type):
 try:
 self.connection.delete_db_user(self.sesskey, db_name, db_type)
 except xmlrpclib.Fault as e:
 print 'ignored error:', e
 try:
 self.connection.delete_db(self.sesskey, db_name, db_type)
 except xmlrpclib.Fault as e:
 print 'ignored error:', e
</code></pre>

File fabfile.py: A sample fabric script to generate session key, needed only if USE_SESSKEY=True

<pre><code>from fabric.api import *
from fabric.operations import run, put
from webfaction import Webfaction
import io

env.hosts = ["webfactionusername@webfactionusername.webfactional.com"]
env.password = "webfactionpassword"

def run_test():
 wf = Webfaction()
 wf.login(env.hosts[0].split('@')[0], env.password)
 sesskey_file = '~/sesskey'
 sesskey = wf.sesskey
 try:
 put(io.StringIO(unicode(sesskey)), sesskey_file, mode='0600')
 # put your test code here
 # e.g. run('DJANGO_SETTINGS_MODULE=settings /path/to/virtualenv/python /path/to/manage.py test --testrunner=test_runner.WebfactionTestRunner')
 raise Exception('write your test here')
 finally:
 run("rm -f %s" % sesskey_file)
</code></pre>

blocks|key|3246034|text|被接受的答案对我不起作用。它太过时了，不能在我的djano+1.5遗留代码库上运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3246035|我通过创建替代测试运行器并更改django设置来提供所有必需的配置并使用新的测试运行器，从而编写了一个blogpost+entirely+describing+how+I+solved+this+issue。|offset|length|3246036|entityMap|0|LINK|mutability|MUTABLE|url|http://tinystruggles.com/2014/10/20/django_tests_with_mirror_database.html^0|0|1F|1G|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

The accepted answer didn't work for me. It's so outdated, that it didn't run on my legacy codebase with djano 1.5.

I wrote a <a href="http://tinystruggles.com/2014/10/20/django_tests_with_mirror_database.html" rel="nofollow noreferrer">blogpost entirely describing how I solved this issue</a> by creating an alternative test runner and changing django settings to provide all the required config and to use new test runner.

blocks|key|3031981|text|简单的解决方法：随意更改django/db/backends/base/creation.py中的TEST_DATABASE_PREFIX。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|3031982|entityMap^0|0|7|C|Z|1D|K|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|D]|$9|N|A|O|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|P|8|@]|E|@]|F|$]]]|H|$]]

Simple workaround: change <code>TEST_DATABASE_PREFIX</code> in <code>django/db/backends/base/creation.py</code> as you like.

blocks|key|299465|text|在使用单元测试时，您需要指定sqlite引擎。打开settings.py并添加just+after+DATABASES部分：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|299466|import+sys
if+'test'+in+sys.argv+or+'test_coverage'+in+sys.argv:+#Covers+regular+testing+and+django-coverage
++++DATABASES['default']['ENGINE']+=+'django.db.backends.sqlite3'
++++DATABASES['default']['NAME']+=+':memory:'|code-block|syntax|javascript|299467|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You need to specify a sqlite ENGINE when using unit tests. Open the settings.py and add the just after DATABASES section:
<pre><code>import sys
if 'test' in sys.argv or 'test_coverage' in sys.argv: #Covers regular testing and django-coverage
 DATABASES['default']['ENGINE'] = 'django.db.backends.sqlite3'
 DATABASES['default']['NAME'] = ':memory:'
</code></pre>

I'm trying to run

<pre><code>./manage.py test
</code></pre>

But it tells me

<blockquote>
 Got an error creating the test database: permission denied to create database
</blockquote>

Obviously it doesn't have permission to create the database, but I'm on a shared server, so there's not much I can do about that. I can create a new database through the control panel but I don't think there's any way I can let Django do it automatically.

So, can't I create the test database manually and instead tell Django to flush it every time, rather than recreating the whole thing?

Choose test database?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在试着跑./manage.py test但它告诉我在创建测试数据库时出错:创建数据库的权限被拒绝显然，它没有创建数据库的权限，但我在共享服务器上，因此对此我无能为力。我可以通过控制面板创建一个新的数据库，但我不认为有任何方法可以让Django自动完成。那么，我不能手动创建测试数据库，让Django每次刷新它，而不是重...

问选择测试数据库？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问选择测试数据库？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问选择测试数据库？
EN