Fix CLOB/BLOB insertion when prepared_statements is false #2485
+63
−0
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.
Summary
prepared_statements: falseprepared_statements: trueThis commonly occurs in Rails 8 development environments where
config.active_record.query_log_tags_enabled = true(the default) causes Rails to automatically disable prepared statements.Changes
before_create :record_lobs_for_createcallbackafter_create :enhanced_write_lobscallbackrecord_lobs_for_createmethod to track non-nil LOB columns on createprepared_statementsis enabled (LOB data already written via temporary LOB binding intype_cast())Test plan
prepared_statements: falseFixes #2477
Fixes #2483