I think your problem is probably that the "garbo" database user doesn't have the necessary permissions on that table. You can fix this in `database/schema/security.cfg`: the `[garbo]` section will need something like `public.signedcodeofconduct = SELECT, UPDATE`.
security.cfg changes are applied automatically on rollouts to our various instances, but in a development setup you'll need to run `for db in launchpad_empty launchpad_dev_template launchpad_dev launchpad_ftest_template launchpad_ftest_playground; do database/schema/security.py -d $db; done` (or `make schema`, but that wipes and replaces your local database rather than changing its permissions in place).
I think your problem is probably that the "garbo" database user doesn't have the necessary permissions on that table. You can fix this in `database/ schema/ security. cfg`: the `[garbo]` section will need something like `public. signedcodeofcon duct = SELECT, UPDATE`.
security.cfg changes are applied automatically on rollouts to our various instances, but in a development setup you'll need to run `for db in launchpad_empty launchpad_ dev_template launchpad_dev launchpad_ ftest_template launchpad_ ftest_playgroun d; do database/ schema/ security. py -d $db; done` (or `make schema`, but that wipes and replaces your local database rather than changing its permissions in place).