Uploaded image for project: 'MusicBrainz Server'
  1. MusicBrainz Server
  2. MBS-9595

Submitting release fails on constraint "only_non_empty" (recording.name) or "recording_length_check"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Release editor
    • None

      https://sentry.metabrainz.org/metabrainz/musicbrainz-server/issues/600/

      DBD: :Pg::st execute failed: ERROR:  new row for relation "recording" violates check constraint "only_non_empty"
      DETAIL:  Failing row contains (22033422, ecbe6ae1-1ae5-4491-84a3-f14c333765d8, , 2139326, null, , 0, 2018-01-04 07:21:36.668207+00, f). [for Statement "INSERT INTO recording (artist_credit,name,length,gid) VALUES (?,?,?,?) RETURNING id" with ParamValues: 1='2139326', 2='', 3=undef, 4='ecbe6ae1-1ae5-4491-84a3-f14c333765d8']
        File "Connector.pm", line 49, in MusicBrainz::Server::Connector::__ANON__
          $exception->throw( sqlstate => $state, message => $msg );
        File "CoreEntity.pm", line 95, in MusicBrainz::Server::Data::CoreEntity::insert
          };
        File "Create.pm", line 165, in MusicBrainz::Server::Edit::Medium::Create::_insert_hash
          })->{id};
        File "Create.pm", line 47, in MusicBrainz::Server::Edit::Generic::Create::insert
          my $hash   = $self->_insert_hash(clone($self->data));
        File "Edit.pm", line 556, in MusicBrainz::Server::Data::Edit::create
          $edit->insert;
      ...
      (11 additional frame(s) were not displayed)
      

            Unassigned Unassigned
            dev-sentry Dev through Sentry
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                Version Package