Fixed #11969 -- `Field.post_create_sql` hook should not be called for unmanaged models. Thanks, jtiai for report.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@12313 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
ff6b44980a
commit
8f46cdec97
|
@ -151,12 +151,12 @@ def custom_sql_for_model(model, style, connection):
|
||||||
output = []
|
output = []
|
||||||
|
|
||||||
# Post-creation SQL should come before any initial SQL data is loaded.
|
# Post-creation SQL should come before any initial SQL data is loaded.
|
||||||
# However, this should not be done for fields that are part of a a parent
|
# However, this should not be done for models that are unmanaged or
|
||||||
# model (via model inheritance).
|
# for fields that are part of a parent model (via model inheritance).
|
||||||
nm = opts.init_name_map()
|
if opts.managed:
|
||||||
post_sql_fields = [f for f in opts.local_fields if hasattr(f, 'post_create_sql')]
|
post_sql_fields = [f for f in opts.local_fields if hasattr(f, 'post_create_sql')]
|
||||||
for f in post_sql_fields:
|
for f in post_sql_fields:
|
||||||
output.extend(f.post_create_sql(style, model._meta.db_table))
|
output.extend(f.post_create_sql(style, model._meta.db_table))
|
||||||
|
|
||||||
# Some backends can't execute more than one SQL statement at a time,
|
# Some backends can't execute more than one SQL statement at a time,
|
||||||
# so split into separate statements.
|
# so split into separate statements.
|
||||||
|
|
Loading…
Reference in New Issue