#16550: Django should load custom SQL when testing
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
elver.loho@… | Status: reopened
Type: New | Component: Database layer
feature | (models, ORM)
Milestone: | Severity: Normal
Version: 1.3 | Keywords:
Resolution: | Has patch: 0
Triage Stage: | Needs tests: 0
Unreviewed | Easy pickings: 1
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by elver.loho@…):
* status: closed => reopened
* type: Bug => New feature
* resolution: wontfix =>
Comment:
In that case I request this as a feature. It is downright moronic that I
have to work around Django's deliberate limitation in order to test more
advanced code.
I said this before and will repeat it here: I am NOT using SQL to load
data into the database before testing. I am using SQL to create custom
data types in the database before I can even load my data in it. Fixtures
DO NOT help me in any way when trying to solve this problem. I am not
putting data into the database -- I am extending the capabilities of the
database.
--
Ticket URL: <https://code.djangoproject.com/ticket/16550#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
