This seems antithetical to the design goals of Django's ORM (e.g. *not*
being an interface for SQL but an abstraction layer for managing objects).
While it may not be as pretty to execute your raw SQL in your setUp method,
that seems like the right way to handle cases of specialized SQL such as
Hi Viktor,
Django already supports SQL fixtures:
http://docs.djangoproject.com/en/dev/howto/initial-data/#initial-sql
SQL fixtures have a very important limitation in the context of testing. You
can't use them to create data; but you said you wanted to create a column and a
stored procedure, s
Hi,
This is a bit of a continuation from this email in the other django
group: https://groups.google.com/forum/#!topic/django-users/rRkYNt-cQOg
The gist of it is this. More complex apps probably deal with with stored
procedures, and columns not under direct django control (which is the case
