Unexpected read locks on objects with same name in same schema

Detail name	Value
Changelog Number	14729
Type	Bug
Status	Resolved
Affected Versions	Exasol 7.0.0, Exasol 7.1.0, Exasol 8.0.0
Fix Versions	Exasol 7.1.13, Exasol 8.4.0
Resolution Date	2022-08-24

Description

If multiple objects in a schema share the same name, e.g. a table and a script with the name T in schema S, a read lock on one of the objects causes a read lock on all objects with the same name in this schema.
Those additional locks might cause unexpected transaction conflicts.

Workaround

Use distinct names per schema.

Fix

Those additional locks are removed immediately, avoiding transaction conflicts.