[Django] #18954: Initial sql data documentation
Django
-------------------------------+--------------------
Reporter: jli | Owner: nobody
Type: New feature | Status: new
Component: Documentation | Version: 1.4
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
Ok on this page:
https://docs.djangoproject.com/en/dev/howto/initial-data/#providing-
initial-sql-data
I think it would be nice to add that if for some reason you're using
models as a directory with __init__.py that import every sub modules in
there, you need to actually move the sql folder inside your models folder.
So to be clear:
usual setups is :
my_app/
sql/
mymodel.sql
models.py --> myModel
the setup that needs documentation:
my_app/
models/
mymodelgroup.py --> myModel
anothermodelgroup.py --> anotherModel
sql/
mymodel.sql
There is no info anywhere about this, I don't know if it's a feature or a
bug by the way.
But it make sense I think to move the sql script inside the models folder
it it's actually a folder.
Cheers!
--
Ticket URL: <https://code.djangoproject.com/ticket/18954>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: jli | Owner: nobody
Type: New feature | Status: new
Component: Documentation | Version: 1.4
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timo):
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/18954#comment:1>
Django
Reporter: jli | Owner: nobody
Type: New feature | Status: closed
Component: Documentation | Version: 1.4
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timo):
* status: new => closed
* resolution: => wontfix
Comment:
I'm going to "won't fix" this and just fix the bug (#14300).
--
Ticket URL: <https://code.djangoproject.com/ticket/18954#comment:2>