sqlglot-upgrade

To update SQLFrame for a new sqlglot version, follow a systematic process: update the dependency in setup.py, identify API removals, migrate from invoke_anonymous_function to new sqlglot expression classes, and fix resulting test failures.

Migrating from invoke_anonymous_function to sqlglot expression classes involves replacing older function invocation methods with newer expression classes to achieve cleaner, more efficient SQL transpilation and remove dialect-specific workarounds.

Handling sqlglot API removals during an upgrade requires detecting the removed APIs in your codebase, adapting the affected function calls to use the updated sqlglot expression classes, and running tests to verify the dependency migration.

You should remove dialect-specific workarounds during a sqlglot code migration when new expression classes are discovered that natively support the required SQL transpilation, allowing you to replace custom logic with standard library features.

Yes, the sqlglot upgrade process requires fixing broken tests after updating setup.py, as adapting the codebase to API changes and migrating to new expression classes often causes test failures that must be resolved to ensure a smooth transition.

The best way to discover new sqlglot expression classes after an upgrade is to systematically review the updated library's API surface, identify classes that replace invoke_anonymous_function, and integrate them to eliminate obsolete dialect-specific workarounds.