Skip to content

Generate invalid sql for IndexCreateStatement::cond_where on MySQL …#1067

Open
Huliiiiii wants to merge 1 commit intoSeaQL:masterfrom
Huliiiiii:fix-1066
Open

Generate invalid sql for IndexCreateStatement::cond_where on MySQL …#1067
Huliiiiii wants to merge 1 commit intoSeaQL:masterfrom
Huliiiiii:fix-1066

Conversation

@Huliiiiii
Copy link
Copy Markdown
Member

Closes #1066

@Huliiiiii Huliiiiii requested review from Expurple and tyt2y3 April 16, 2026 02:14
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6414c2e89d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/backend/mysql/index.rs
Copy link
Copy Markdown
Member

@Expurple Expurple left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would explicitly document on those methods why we intentionally generate invalid SQL for MySQL, and reference the issue.

The decision itself is OK to me. Probably makes more sense to crash the query, than to crash the entire app with a panic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MySQL backend silently drops cond_where on IndexCreateStatement

2 participants