db migration issues
Bug #721762 reported by
Ronnie
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_
approved boolean DEFAULT false NOT NULL,
approved_date date,
expires_date date,
...
);
Production
CREATE TABLE teams (
...
provides_
approved boolean NOT NULL,
approved_date timestamp with time zone,
expires_date timestamp with time zone,
...
);
Changed in loco-directory: | |
importance: | Undecided → High |
description: | updated |
Changed in loco-directory: | |
status: | New → Confirmed |
To post a comment you must log in.