settings.py: Add 'schema' to database configuration

Django doesn't use this setting, but South consults it when
inspecting tables for their constraints.  The fact that we store our
tables in the 'humbug' schema was causing South to fail to find our
table constraints (it was looking in the 'public' schema) and
therefore throw an exception when we try to remove the unique
constraint in migration 0002.

(imported from commit 4230338a7b78329a759339b2f9fcd277137b7f32)

humbug/settings.py

@@ -40,6 +40,7 @@ if DEPLOYED:
         'USER': 'humbug',
         'PASSWORD': '', # Authentication done via certificates
         'HOST': '10.254.4.99',
+        'SCHEMA': 'humbug',
         'OPTIONS': {
             # Note that 'verify-ca' only checks that the server certificate was
             # signed by a trusted root.  You need 'verify-full' if you want to
@@ -63,7 +64,8 @@ elif False:
         'NAME': 'humbug',
         'USER': 'humbug',
         'PASSWORD': 'yuHavmefbek5',
-        'HOST': 'localhost'
+        'HOST': 'localhost',
+        'SCHEMA': 'humbug'
         }
 
 # Local time zone for this installation. Choices can be found here: