I tried to add a couple of secondary types to a release, and received the following Internal Server Error:

Internal Server Error
Oops, something went wrong!

Error:

Caught exception in MusicBrainz::Server::Controller::ReleaseGroup->edit "The edit could not be created.
POST: $VAR1 =

{ 'edit-release-group.artist_credit.names.0.artist.id' => '2121', 'edit-release-group.name' => 'Director\'s Cut', 'edit-release-group.secondary_type_ids' => [ '1', '5' ], 'gc-keepuppercase' => 'on', 'edit-release-group.primary_type_id' => '1', 'edit-release-group.artist_credit.names.0.name' => 'Kate Bush', 'edit-release-group.edit_note' => '', 'edit-release-group.artist_credit.names.0.join_phrase' => '', 'edit-release-group.artist_credit.names.0.artist.name' => 'Kate Bush', 'gc-mode' => 'English', 'edit-release-group.comment' => '' }

;

Exception:$VAR1 = 'update_row called with no columns to update at lib/MusicBrainz/Server/Data/ReleaseGroup.pm line 452
at lib/Sql.pm line 290
';
at lib/MusicBrainz/Server/Controller.pm line 101"
Stack trace:
line 97 MusicBrainz::Server::Controller
line 101 MusicBrainz::Server::Controller
line 134 MusicBrainz::Server::Controller
line 37 MusicBrainz::Server::Controller::Role::Edit
line 265 MusicBrainz::Server
Request data:

$VAR1 = {
'query_parameters' => {},
'body_parameters' =>

{ 'edit-release-group.artist_credit.names.0.artist.id' => '2121', 'edit-release-group.name' => 'Director\'s Cut', 'gc-keepuppercase' => 'on', 'edit-release-group.secondary_type_ids' => [ '1', '5' ], 'edit-release-group.artist_credit.names.0.name' => 'Kate Bush', 'edit-release-group.primary_type_id' => '1', 'edit-release-group.edit_note' => '', 'edit-release-group.artist_credit.names.0.join_phrase' => '', 'edit-release-group.artist_credit.names.0.artist.name' => 'Kate Bush', 'gc-mode' => 'English', 'edit-release-group.comment' => '' }

};

URL: http://test.musicbrainz.org/release-group/f857c209-1a7d-45dd-97cc-62c30b91be01/edit

We're terribly sorry for this problem. Please wait a few minutes and repeat your request — the problem may go away.

If the problem persists, please report a bug and include any error message that is shown above.

Please be sure to include the stack trace and request data shown above!