db migration issues

Bug #721762 reported by Ronnie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LoCo Team Portal
Confirmed
High
Unassigned

Bug Description

The production database is different from the code in django

These difference i could find:

Mine
CREATE TABLE teams (
    ...
    provides_support boolean DEFAULT true NOT NULL,
    approved boolean DEFAULT false NOT NULL,
    approved_date date,
    expires_date date,
    ...
);

Production
CREATE TABLE teams (
    ...
    provides_support boolean NOT NULL,
    approved boolean NOT NULL,
    approved_date timestamp with time zone,
    expires_date timestamp with time zone,
    ...
);

Ronnie (ronnie.vd.c)
Changed in loco-directory:
importance: Undecided → High
Ronnie (ronnie.vd.c)
description: updated
Changed in loco-directory:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.