fix(databricks): string escaper

[betodealmeida]

SUMMARY

The Databricks SQLAlchemy dialect we use has a bug when escaping single quotes: it doubles the single quote, instead of using a backslash. For example, a value of O'Hara will be rendered in the SQL as O''Hara, which is correct for most databases, but for Databricks should be O\'Hara.

Upgrading to the latest databricks-sqlalchemy package fixes the issue, but requires SQLAlchemy 2.x. The 1.x line of databricks-sqlalchemy has the bug as well. Note, we're using the unnoficial sqlalchemy-databricks package instead, so we should consider changing to the 1.x version of the official one.

For now, this PR solves the problem by monkeypatching a custom string escaper into the the dialect.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before:

After:

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[korbit-ai]

I was unable to post the issues I found. This could be because a force push or squash has changed the commit history since I scanned this pull request. You can get another review by commenting /korbit-review.

[Vitor-Avila]

Thanks for porting the fix!