Show actual exception instead encountered unsupported duckdb type null #8236
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a model view is created without materialize: true on S3 data,
the table listing and preview were previously showing the error:
unsupported duckdb datatype: "NULL"instead of the actual exception.unsupported duckdb datatype: "NULL".This issue will be resolved once we move to the new listTables implementation (base PR).
In that version, errors will no longer occur during listing — they’ll only be raised when fetching table metadata (column name, and data type). As a result, only the affected table will report an error.
Checklist: