brodiealexander commented on PR #2092: URL: https://github.com/apache/iceberg-rust/pull/2092#issuecomment-3824300902
So, after getting a good night's rest I've worked out that for most of these cases it's better and easier to just `SELECT *` and then use the query results to check for column presence. However, it's still unclear what should be done for `register_table`, `drop_table`, and `rename_table`. Can there be a table and view with the same name, or are they mutually exclusive? If they're mutually exclusive, drop_table and rename_table are easily solvable. `register_table` is a little more complicated. Should we keep backend-specific code for detecting `iceberg_type` and have two separate code paths in `register_table` for either case? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
