** Description changed: 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 DEFAULT true NOT NULL, - approved boolean DEFAULT false NOT NULL, - approved_date date, - expires_date date, - ... + ... + provides_support boolean NOT NULL, + approved boolean NOT NULL, + approved_date timestamp with time zone, + expires_date timestamp with time zone, + ... ); - - Mine - CREATE TABLE teams ( - ... - provides_support boolean NOT NULL, - approved boolean NOT NULL, - approved_date timestamp with time zone, - expires_date timestamp with time zone, - ... - );
-- You received this bug notification because you are a member of loco- directory-dev, which is the registrant for loco-directory. https://bugs.launchpad.net/bugs/721762 Title: db migration issues Status in LoCo Directory: New 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, ... ); _______________________________________________ Mailing list: https://launchpad.net/~loco-directory-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~loco-directory-dev More help : https://help.launchpad.net/ListHelp
