Schema default expression #18858
Merged
Schema default expression #18858
Conversation
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
markstory
force-pushed
the
schema-default-expression
branch
from
7d0065b to
ebcd685
Compare
markstory
added a commit
to cakephp/migrations
that referenced
this pull request
Aug 25, 2025
With the changes from cakephp/cakephp#18858 these changes should resolve the regressions around `Literal` values raised in cakephp/cakephp#18845
markstory
added a commit
to cakephp/migrations
that referenced
this pull request
Sep 1, 2025
* Fix Literal default values With the changes from cakephp/cakephp#18858 these changes should resolve the regressions around `Literal` values raised in cakephp/cakephp#18845 * Bump cake version to test against QueryExpression fix * Revert "Bump cake version to test against QueryExpression fix" This reverts commit a7ee824.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add support for
QueryExpressionas a default value when generating schema. This will help resolve some compatibility issues in migrations in a more robust way. Refs #18845