Postgres doesn't like it if you use 0 as the default for a booleanfield
previous migrations already create these columns so we don't need to create them again

postgres doesn’t like it if we try to add a column that already exists
the profile app has a dependency on webresponse already existing
the search app has a dependency on the profile already existing
postgres doesn't like it if we try to alter a time field to an integer field. better to just drop it and add it again.