I think it's irrelevant because it's not an error like "the playlist is malformed", it's something at the DB level that means either a DB disconnection or some error in the code. In any case, we could define 'createError' 'updateError', etc events and emit both with the same message