Skip to content

Refactor: migration to sqlparser-rs instead of sea-query#2

Draft
awolverp wants to merge 1 commit into
masterfrom
migrate
Draft

Refactor: migration to sqlparser-rs instead of sea-query#2
awolverp wants to merge 1 commit into
masterfrom
migrate

Conversation

@awolverp

@awolverp awolverp commented Jun 18, 2026

Copy link
Copy Markdown
Owner

Based on feedback received from my friends, I decided to migrate to a customized sqlparser-rs.

For several reasons:

  • Complete elimination of panic errors and greater confidence in the library in production.
  • Support for more than 10 dialects:
    • BigQuery
    • ClickHouse ( maybe )
    • DataBricks
    • DuckDB
    • Hive
    • MsSQL
    • MySQL
    • Oracle
    • PostgreSQL
    • RedShift
    • Snowflake
    • Spark
    • SQLite
    • TeraData
  • Support for all data types.
  • This opens the door to adding SQL parsing capabilities in the future.
  • I will be able to offer a better and more complete interface to developers.
  • All SQL features become available without any limitations.
  • This greatly simplifies building an ORM and keeps options open.

Why customized sqlparser-rs:

  • To support prepared statements. We will use named parameters.

I'll try to keep this update as backward-compatible as possible, but I can't make any guarantees.

@awolverp awolverp added the enhancement New feature or request label Jun 18, 2026
@awolverp awolverp changed the title Migration to sqlparser-rs instead of sea-query Refactor: migration to sqlparser-rs instead of sea-query Jun 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant