MySQL Bugs: #120889: Contribution: Implement extended capability flags and metadata caching

Bug #120889	Contribution: Implement extended capability flags and metadata caching
Submitted:	7 Jul 16:41	Modified:	30 Jul 11:27
Reporter:	OCA Admin (OCA)	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	Connector / J	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
This bug tracks a contribution by diego DUPIN (Github user: kalebaran), as described in http://github.com/mysql/mysql-connector-j/pull/127

How to repeat:
See description

Suggested fix:
See contribution code attached

Contribution submitted via Github - Implement extended capability flags and metadata caching (*) Contribution by diego DUPIN (Github kalebaran, https://github.com/mysql/mysql-connector-j/pull/127#issuecomment-4905312284): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: git_patch_3954888947.txt (text/plain), 14.09 KiB.

Thank you for the contribution and for the work that went into implementing this feature.

After review, we have decided not to merge this pull request in its current form and will close it.

The proposed change is broader than a Connector/J-local optimization. It adds support for MariaDB-defined handshake capabilities and corresponding result-set protocol behavior. Server-facing protocol changes need to be designed, approved, and owned at the MySQL platform level rather than introduced independently in a single Connector.

MySQL Connector/J does not support this MariaDB-specific protocol extension, and adding such support is outside the scope of this pull request. Accepting the patch would create an ongoing compatibility expectation requiring a clearly defined support scope, documented negotiation and fallback behavior, integration testing against the applicable MariaDB Server versions, regression coverage demonstrating that MySQL Server behavior remains unchanged, and clear ownership for continued maintenance as both implementations evolve. That support and maintenance framework is not part of the Connector/J project’s current scope.

Any external contribution that proceeds toward acceptance must also satisfy the project’s normal OCA-coverage and source-provenance requirements. These checks are separate from the product and engineering decision described above. We are not making an adverse finding on either point by closing this pull request.

If metadata caching is proposed as a MySQL feature, the appropriate starting point would be a MySQL Server protocol proposal, including a reviewed specification, a corresponding server implementation, interoperability and regression tests, and a plan for the relevant Connectors. Any such proposal would be evaluated independently through the normal design and contribution process.

This decision is based on protocol ownership, compatibility scope, testability, and long-term maintainability. It is not based on assumptions about the contributor’s motivation or about which users may benefit from the change.

Thank you again for engaging with the project.