diff --git a/icekit_events/migrations/0012_auto_20160706_1606.py b/icekit_events/migrations/0012_auto_20160706_1606.py
index <HASH>..<HASH> 100644
--- a/icekit_events/migrations/0012_auto_20160706_1606.py
+++ b/icekit_events/migrations/0012_auto_20160706_1606.py
@@ -24,6 +24,6 @@ class Migration(migrations.Migration):
             # No-op: I haven't yet found a way to make this reversible in the
             # way you would expect without unique constraint DB errors, whereas
             # it works (according to unit tests at least) with a no-op.
-            "",
+            "UPDATE django_content_type SET app_label=app_label WHERE app_label='NONE!'",
         ),
     ]
Make migration reverse no-op a valid SQL query

When using a PostgreSQL database with Django <I> empty reverse query
statements in DB migrations cause an error, so we replace the empty
no-op statement with a valid query that still does nothing so the
reverse migration will work in this case.

This problem doesn't seem to affect Django <I>, which must be smarter
about accepted but not actually running empty statements in DB
migrations.