https://github.com/lucee/Lucee/commit/818f0830152b3836de0d274869158cef91025ffb

https://github.com/lucee/Lucee/commit/60295f964e75ab0cb381dcaa21eeaffb7a07102f

solving the issue reported by and makes sure we always have a pattern set (default %), if you have still an unrelated issue to this fix with cfdbinfo, please open another ticket and link it here.
normally a ticket should never point out more than one issue and for sure NOT address more than one issue. addressing more than one issue at once can produce hard to reverse engineering regression issues.

cannot reproduce the issue with Lucee 5.3.1

to the description:
i cannot reproduce with MySQL 5 or 8, also type "version" does NOT call getTables at all.
we will make sure 'tableNamePattern' is never passed as null or empty string.

Lucee 5.3 now bundles the MySQL Connector/J 8.0.15 driver which means this issue may become a critical problem for users who are upgrading as it's a significant change in behaviour. We've hit the same problem that Jonathan has described above;

• Lucee 5.2.9.31 using MySQL Connector/J 5.1.40: calling cfdbinfo to introspect tables or columns will only return data for the database that is contained in the connection string

• Lucee 5.3.1.95 using MySQL Connector/J 8.0.15: calling cfdbinfo to introspect tables or columns will return matches for all databases that the credentials in the connection string can access

The majority of our apps do not store the actual database name in a variable that can easily be accessed, so it's not trivial to add the "dbname" attribute to all calls to cfdbinfo.

The Connector/J docs for the connection string URL seem to indicate that the database name provided in the connection string should be the default database;
https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-reference-jdbc-url-format.html#idm139642450258592

Would it be appropriate for Lucee MySQL connections to call Connection.setCatalog() method to specify the default database if the driver is essentially no longer doing this for us, or might there be some other workaround?

In addition, it seems that MySQL Connector/J 8.0.15 and cfdbinfo are now significantly slower when run against the same database (regardless of the number of columns in a table, the performance is always the same).

• Lucee 5.2.9.31 using MySQL Connector/J 5.1.40: Execution Time: 8ms

• Lucee 5.3.1.95 using MySQL Connector/J 8.0.15: Execution Time: 128ms

For applications that do DB introspection on dozens of tables during startup (or at other times) this performance difference is almost a show stopper. Something that should take less than half a second might end up taking 7 or 8 seconds or more.

I haven't yet tried to use the older driver in Lucee 5.3 as I've run out of time for today.

P.S. There are a lot of unit tests that use the older MySQL Connector/J driver in the connection string, those might need to be updated, and could potentially help surface other issues that we might not have run into yet?