Report Fails to Insert If Metadata Exceeds Column Limits

[Thermalight]

Description:

When a report is inserted into the database, metadata is extracted from checkpoints and stored in specific columns. However, if any extracted metadata exceeds the column's constraints (e.g., length limits or data type mismatches), the entire report fails to insert. This results in the loss of the full report and its associated logs, making debugging difficult.

Expected Behavior:

The report should always be inserted into the database, even if metadata cannot be inserted.
If metadata exceeds column constraints, it should either be truncated (if applicable) or ignored, while still logging an error for debugging purposes.

Proposed Solution Options:

• Implement error handling to catch metadata insertion failures.
• Allow the main report to be inserted even if metadata cannot be stored.
• Log a warning when metadata is ignored due to size or format issues.

[checkiecheck]

As a general improvement is the current logging on db inserts not showing the bind variables. It would already help if those (bing values) are shown on errors.

insert could be retried with null value for the column with error in this case, the improved log will show the required intell to analyse and act on.

[jacodg]

Why a null value? I would say that the Ladybug can truncate the string to the max length for the column before doing the insert?