implement DEFAULT, and default syntax {expr}??#189
Merged
jongleb merged 2 commits intoygrek:masterfrom Apr 29, 2025
Merged
Conversation
DEFAULT, and default syntax {expr}??
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.
Description
This PR adds support to
DEFAULTand special{expr}??syntax that generates a regular option when insert.The main motivation is to not make DEFAULT part of regular expr, because in sql this DEFAULT is only available on insert and update.
That is, writing like this will not be valid and an error will be caught:
On the contrary, using this on insert/update will just generate option, and if there is no data,
DEFAULTwill be generated, similar to how it works for filtering and skipping{expr}?syntax.example taken from tests:
The generated result: