Browse files

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
  • Loading branch information...
1 parent ff6b449 commit 8f46cdec97b5203481a56dc637a44fd0e284969d @jbronn jbronn committed Jan 27, 2010
Showing with 6 additions and 6 deletions.
  1. +6 −6 django/core/management/sql.py
View
12 django/core/management/sql.py
@@ -151,12 +151,12 @@ def custom_sql_for_model(model, style, connection):
output = []
# 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
- # model (via model inheritance).
- nm = opts.init_name_map()
- post_sql_fields = [f for f in opts.local_fields if hasattr(f, 'post_create_sql')]
- for f in post_sql_fields:
- output.extend(f.post_create_sql(style, model._meta.db_table))
+ # However, this should not be done for models that are unmanaged or
+ # for fields that are part of a parent model (via model inheritance).
+ if opts.managed:
+ post_sql_fields = [f for f in opts.local_fields if hasattr(f, 'post_create_sql')]
+ for f in post_sql_fields:
+ output.extend(f.post_create_sql(style, model._meta.db_table))
# Some backends can't execute more than one SQL statement at a time,
# so split into separate statements.

0 comments on commit 8f46cde

Please sign in to comment.