I don't remember why E_TASK_TABLE_DEFAULT_STATE was needed when e-calendar-table.etspec already specifies a default ETableState. Some of the column numbers it was referencing weren't even valid. Removing it seems to make no difference in Evolution.