Row timestamps: Internal metadata columns blocked (Pending)¶

Attention

This behavior change is in the 2026_07 bundle.

For the current status of the bundle, refer to Bundle history.

When this behavior change bundle is enabled, SQL that references the undocumented internal metadata columns METADATA$PERSISTED_ROW_MODIFIED_TIMESTAMP and METADATA$FILE_TXN_END_TIME fails with an invalid identifier error. These columns were never part of the documented row timestamp feature. Continue to use METADATA$ROW_LAST_COMMIT_TIME.

Before the change:

Queries could reference METADATA$PERSISTED_ROW_MODIFIED_TIMESTAMP and METADATA$FILE_TXN_END_TIME. Those columns aren’t documented and aren’t part of the supported row timestamp API.

After the change:

When the 2026_07 behavior change bundle is enabled in your account, any SQL that references METADATA$PERSISTED_ROW_MODIFIED_TIMESTAMP or METADATA$FILE_TXN_END_TIME fails with an invalid identifier error. This includes statements in stored procedures, tasks, dynamic tables, generated SQL from frameworks, test utilities, and internal tooling.

METADATA$ROW_LAST_COMMIT_TIME is unchanged and remains the supported metadata column for row timestamps.

Ref: 2406