You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After CREATE -> DROP -> CREATE sequence we have both old and new trigger objects in the metadata cache. This may lead to either unexpected behavior at runtime or "invalid BLOB ID" errors related to the debug information blob (which is already garbage collected for the old trigger instance).
It seems that only database-level triggers are affected.
description: After CREATE -> DROP -> CREATE sequence we have both old and new trigger objects in the metadata cache. This may lead to either unexpected behavior at runtime or "invalid BLOB ID" errors related to the debug information blob (which is already garbage collected for the old trigger instance). => After CREATE -> DROP -> CREATE sequence we have both old and new trigger objects in the metadata cache. This may lead to either unexpected behavior at runtime or "invalid BLOB ID" errors related to the debug information blob (which is already garbage collected for the old trigger instance).
It seems that only database-level triggers are affected.
Submitted by: @dyemanov
After CREATE -> DROP -> CREATE sequence we have both old and new trigger objects in the metadata cache. This may lead to either unexpected behavior at runtime or "invalid BLOB ID" errors related to the debug information blob (which is already garbage collected for the old trigger instance).
It seems that only database-level triggers are affected.
Commits: 792fd3d
The text was updated successfully, but these errors were encountered: