Valid index names throw error in schema introspection

[keulinho]

Bug Report

Q	A
Version	Deprecation in 4.3.0, will be error in 5.0
Previous Version if the bug is a regression	x.y.z

Summary

At least in MySQL/MariaDB dots are allowed as the name of an index/constraint. However if you use that the introspection fails:

Unable to parse object name: An unqualified name must consist of one identifier, 3 given.

On Introspection the names from the DB should be accepted by DBAL, even if it does not support to create that schema in the first place.
I think the root cause is that the names coming from the actual DB schema are not treated as quoted and therefore parsed again.

However based on the changelog here: 2240b26 the name should be quoted when the name contains a dot.

Current behavior

Indexes/Constraints with dots lead to deprecations on schema introspection.

Expected behavior

Valid names for the DB don't lead to errors on DBAL side

How to reproduce

Add a index/constraint with a dot in the name to a table
call SchemaManager::introspectTable() on that table

[derrabus]

However based on the changelog here: 2240b26 the name should be quoted when the name contains a dot.

Maybe that's the solution: The introspection should read such names as a quoted identifier? Do you want to work on a fix?

[keulinho]

Looks like it was fixed in 5.0.0 here: 92dea81

still this throws deprecations in 4.3.x for cases that will be supported