You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I eluded to this issue in #122 (comment), but not all of duckdb's exactly match snowflakes.
Now, at least, I actually have a concrete location in which it negatively affects my ability to test 😆, i.e. information_schema.tables's missing last_altered column.
My first thoughts would be:
I assume we can't mutate the duckdb information_schema
if this is something you want to support fixing, I could attempt creating a _fs_information_schema with at least a view pointing at the original with the missing column
Seems impractical to actually support the semantics behind, for example, that column(?)
Search every query for table references and swap any that point at information_schema to the new schema?
or perhaps just .tables in the short term, since it would otherwise require stubs for every information_schema table, not sure off the top of my head how many there are
The text was updated successfully, but these errors were encountered:
I eluded to this issue in #122 (comment), but not all of duckdb's exactly match snowflakes.
Now, at least, I actually have a concrete location in which it negatively affects my ability to test 😆, i.e.
information_schema.tables
's missinglast_altered
column.My first thoughts would be:
_fs_information_schema
with at least a view pointing at the original with the missing columninformation_schema
to the new schema?.tables
in the short term, since it would otherwise require stubs for every information_schema table, not sure off the top of my head how many there areThe text was updated successfully, but these errors were encountered: