Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[release/6.0] Temporal table support for owned and table splitting scenarios #27369

Closed
wants to merge 1 commit into from
Closed

[release/6.0] Temporal table support for owned and table splitting scenarios #27369

wants to merge 1 commit into from

Commits on Feb 4, 2022

  1. Temporal table support for owned and table splitting scenarios 

    Fix to #26858 - Query: improve TableExpressionBase extensibility by adding annotations
Fix to #26469 - Query: enable temporal tables for table splitting scenarios
Fix to #26451 - Temporal Table: Owned Entities support?

Added annotation infra for TableExpressionBase and annotations for temporal table information. Removed (now unnecessary) temporal specific table expressions.
Also added temporal table support for owned typed and table splitting in general using the annotations to store the temporal information (no need for provider specific logic in places where we didn't have good extensibility)
For table splitting, every entity must explicitly define period start/end columns. They all need to be the same, but if not explicitly provided we try to uniquefy them. We should fix this so that you only need to specify it in one place but it's currently hard to do (hopefully convention layering will make it easier)
    @maumar
    maumar committed Feb 4, 2022
    Configuration menu
    Copy the full SHA
    bf50cf2 View commit details
    Browse the repository at this point in the history