Resolve "Trim SQL query length in catalogue DB failure reason"
All threads resolved!
Merge request reports
Activity
added File catalogue Tape server workflowIn Progress labels
assigned to @jcamarer
added 1 commit
- 3f8badca - Truncate comments and reason for SQL maximum
added 1 commit
- ce2be132 - Truncate comments and reason for SQL maximum
- Automatically resolved by Jorge Camarero Vera
- Automatically resolved by Jorge Camarero Vera
- Resolved by Joao Afonso
I think this looks good. I have just added some minor typo suggestions, which you are free to accept or ignore.
I addition to that, are these changes supposed to cover both taped and user invocations of these catalogue functions?
Shouldn't we still return an error to the user (which can be an operator tool) if it inserts a comment that is too long? I think this is not a problem (1000 characters is too long already), but I leave this observation to your judgement anyway.Edited by Joao Afonso
enabled an automatic merge when the pipeline for 9fc6189e succeeds
requested review from @afonso
enabled an automatic merge when the pipeline for bd0541e0 succeeds
Please register or sign in to reply