[12.x] PostgreSQL virtual columns #57290
Merged
+17
−19
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.
About two weeks ago, PostgreSQL 18 was released which finally supports virtual generated columns. This PR adds support for it - in a backwards compatible manner.
The
virtualAs()
column modifier was officially not support for PostgreSQL and produced SQL that was invalid:With PostgreSQL 18, this syntax is now supported and defaults to a virtual generated column. However, the current implementation was changed to explicitly add the
virtual
keyword to the DDL query - just to be sure in case defaults may change in the future.Additionally, the tests schema builder tests have been changed to now also test virtual columns which had been excluded in the past - because PG didn't support it.