I\'m using unittest2 together with manage.py test, and before it even seems to run any tests, it spews a horrid database error, as below. I\'m in my development environment (actually on a dreamhost se
I am writing a unit test for Django views. class TestLog(unittest.TestCase): \"\"\"Test for Contact\"\"\"
I have a django project that uses a postgres db with a number of UDFs.The UDFs are written in plpythonu.Since plpyhtonu is an untrusted language, only database super users can use it to to create UDFs
I have a model with a FileField. I want to unittest it. django test framework has great ways to manage database and emails. Is ther开发者_运维知识库e something similar for FileFields?
I\'m planing to build some database project. One of the tables have a lot of attributes. My question is: What is better, to divide the the class into 2 separate tables or put all of them into one ta