id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
14300	manage.py sqlcustom fails if models are in a submodule	David Rogers	Fede Heinz	"This is similar to #6961, from what I've seen. According to [http://docs.djangoproject.com/en/1.2/howto/initial-data/#providing-initial-sql-data the docs for 1.2]:

{{{
Django provides a hook for passing the database arbitrary SQL that's executed just after the CREATE TABLE 
statements when you run syncdb. You can use this hook to populate default records, or you could also create
SQL functions, views, triggers, etc.

The hook is simple: Django just looks for a file called sql/<modelname>.sql, in your app directory, where 
<modelname> is the model's name in lowercase.
}}}

This doesn't work when the ""models"" module is a directory instead of a file, i.e. `project/application/models/` vice `project/application/models.py`. Apparently, `sqlcustom` is using similar logic to what was described in #6961, since I can move my `sql/` directory into the `models/` directory  - a la `project/application/models/sql/` - and everything works."	Bug	closed	Core (Management commands)	1.2	Normal	fixed		emyller@… timograham@… vlastimil@…	Accepted	1	0	0	0	0	0