The property mentioned is too complex to be persisted, without its own table. So instead i suggest we make 'LogEntry' able to contain another LogEntry, and this way chaining them together, for when a exception with many inner exceptions occur, to be saved in one chain.
This will allow 'LogEntry' to contain 0 to 1 other LogEntries, laso meaning that it is not reqired for the object to be stored in the database.
The property mentioned is too complex to be persisted, without its own table. So instead i suggest we make 'LogEntry' able to contain another LogEntry, and this way chaining them together, for when a exception with many inner exceptions occur, to be saved in one chain.
This will allow 'LogEntry' to contain 0 to 1 other LogEntries, laso meaning that it is not reqired for the object to be stored in the database.