Repository navigation
Fix table name parsing for INSERT INTO <table> WITH (<hints>) - #1424
Merged
aidanharan merged 2 commits intoOct 26, 2026
Merged
Conversation
Contributor
|
Please backport to 8-1. 👍 |
aidanharan
pushed a commit
that referenced
this pull request
Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Any
INSERTwith a table hint between the table name and the column list fails before it reaches the server:get_raw_table_nametakes everything up to the first(, so the parsed name isbooks WITH.query_requires_identity_insert?runs on every insert and looks that name up, which raises.WITH (TABLOCK)is the documented way to get a minimally loggedINSERT ... SELECT, so right now the only workaround is to go around Active Record.I fixed it in two places:
get_raw_table_namestrips aWITH (...)hint before reading the table name.query_requires_identity_insert?skips past the hint when it looks for the identity column. Without this, an insert with an explicitidstill fails with "IDENTITY_INSERT is set to OFF".INSERT books ...withoutINTOstill isn't handled (it falls through to theFROMbranch). I left that out of this PR.Would you want this backported to
8-1-stable? Happy to open that PR too.