Explorations break for long column names, show `DEFAULT`

[mathemancer]

Description

Under some (not-yet-understood) conditions, the backend mangles Exploration column names, and this results in a situation where the front end can't match returned data to the appropriate columns.

Expected behavior

This should never happen.

To Reproduce

• Go to insider-trading.mathesar.org (password in 1password).
• Create an exploration on the "Derivative Transaction Information" table, including the "Derivative Transaction Surrogate Key" column.
• Notice the problem

Additional context

It may be that this has to do with the length of generated column names when the starting base column name is too long. If an alias name is too long, PostgreSQL itself will mangle it.

[seancolsen]

@mathemancer I've not spent any time troubleshooting this issues in particular. But just from reading your issue body, this stuck out to me:

the length of generated column names

That sounds a lot like the troubleshooting I did here. It could be that this issue is a duplicate of that one. If I recall, it didn't seem particularly easy to fix. Perhaps we could circumvent this for now by using shorter column names in the sample data set.

[mathemancer]

Thanks for the tip, @seancolsen . I'll do some tinkering today, and close this as a duplicate if it is (a duplicate). Interestingly, the symptoms are different in this case, in that the back end is actually returning the right data, but with mismatched column names (i.e., the name on the data column isn't the same as the name in the column metadata). But, I also suspect that the name concatenation bringing identifiers over the 63 byte limit is the underlying cause.