Harmonize drivers to crate<2.2 and sqlalchemy-cratedb<0.43

[amotl]

Problem

One nightly scheduled CI run started failing. A subsystem that still uses SQLAlchemy 1.4 raised this error.

crate.client.exceptions.ProgrammingError:
SQLParseException[line 1:49: no viable alternative at input 'VALUES (%']

Solution

Use previous driver tandem.

References

• Version 2.2.1 fails test cases in two downstream projects crate-python#815
• Status of v0.43.0 sqlalchemy-cratedb#273 (comment)

/cc @bgunebakan, @kneth

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1473ec1d-4066-4cb9-a13e-e4fb1481281d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[bgunebakan]

Hi,
Thank you for your suggestion but I don't understand the motivation behind this change. current cratedb-toolkit 0.0.49 version works correctly because it depends on older packages, pipeline is failing because there is paramstyle changes on new packages but this packages is not used in current cratedb-toolkit version so there is no effect on user experience. We should implement new features that introduced in other packages here to use them other than downgrading and be dependent on older packages.

Best

[amotl]

Hi Bilal. This patch was meant as a mitigation against a single test slot going south after package releases of crate and sqlalchemy-cratedb that will also display the same behaviour when used in production. It will only fix that very slot, as dependency adjustments are exclusively constrained to the corresponding "extra" section optional-dependencies.pymongo.

• Scheduled CI runs for »PyMongo« slot

If you think this is enough of a signal to conduct further actions, together with the other signal coming from the Fivetran adapter, please go ahead.

• Version 2.2.1 fails test cases in two downstream projects crate-python#815

Hereby, I am asking to either work around the issue by adding version constraints (this patch), or about your decision to possibly yank crate-python another time.