Bug #83548 Add registry of uncommitted object to dictionary_client

• Submitted: 26 Oct 2016 12:28
• Modified: 17 Nov 2016 14:55
• Reporter: Jon Olav Hauglid
• Status: Closed
• Category: MySQL Server: Data Dictionary
• Severity: S3 (Non-critical)
• Version: 8.0.1
• OS: Any
• CPU Architecture: Any

[26 Oct 2016 12:28] Jon Olav Hauglid

Description:
Currently the dictionary client only tracks usage of objects from the shared cache (e.g. committed objects).
It would be helpful if the dictionary client also could track uncommitted objects.
This would make it easier for e.g. DDL code as it would not have to track such objects itself.

How to repeat:
n/a

[17 Nov 2016 14:55] Daniel Price

Posted by developer:
 
Fixed as of the upcoming 8.0.1 release, and here's the changelog entry:

Dictionary clients now track uncommitted dictionary objects that are
being modified by DDL statements, making uncommitted changes by the same
session visible to a dictionary client without affecting the dictionary
object cache prior to commit time.