lnav version
v0.13.1

Describe the bug
I was confused about the data I was seeing in SQL summaries that included log_body. The text seemed to be broken when there were long lines.
It looks like maybe this is a feature to display the first part and then the end of message when length exceeds a certain value.
I looked for mention of this in docs but failed.
It does seem quite a good idea in some ways, though in some cases it was creating text shorted than available screen width for the column.
I'm also unclear if selects would work if the search string is in the 'ellipsed' part of the text, but suspect it is just a display trick.
The problem was compounded by the fact that the ... was hardly visible on my screen until I just pasted it from plain text view. It looked more like a "-". (Many small pixels.)

In SQL results:
: (CoreData) [com.apple.coredata:error] fault: Unable to cr⋯eServerEndpointFactory 0x14a60c290 -newEndpoint returned nil

From field:
Family: (CoreData) [com.apple.coredata:error] fault: Unable to create token NSXPCConnection. NSXPCStoreServerEndpointFactory 0x14a60c290 -newEndpoint returned nil

To Reproduce
;select log_body from all_logs where log_body like '%0x14a60c290%';

Maybe if string shortening is done a flag or note could be shown??