Skip to content

HCK-18366: fix boolean false in separate column DEFAULT statements - #99

Merged
taras-dubyk merged 1 commit into
developfrom
fix/boolean-default-false-separate-statement
Oct 30, 2026
Merged

taras-dubyk merged 1 commit into
developfrom
fix/boolean-default-false-separate-statement

Conversation

@Sylvie-P

@Sylvie-P Sylvie-P commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • Boolean default false, column default values in separate statements → SET DEFAULT false
  • Default true, numeric defaults, inline mode unchanged

assignTemplates treated false as missing when filling placeholders, which broke SET DEFAULT false in separate FE statements.

Co-authored-by: Cursor <cursoragent@cursor.com>
@Sylvie-P Sylvie-P changed the title HCK-18362: fix boolean false in separate column DEFAULT statements (YugabyteDB) HCK-18366: fix boolean false in separate column DEFAULT statements Oct 29, 2026
@sonarqubecloud

Copy link
Copy Markdown

@Sylvie-P
Sylvie-P requested a review from taras-dubyk October 29, 2026 17:27
@taras-dubyk
taras-dubyk merged commit d4a301f into develop Oct 30, 2026
8 checks passed
@taras-dubyk
taras-dubyk deleted the fix/boolean-default-false-separate-statement branch October 30, 2026 08:24
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.

2 participants