)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":26285,"name":"wu.chunyang","email":"wchy1001@gmail.com","username":"wu.chunyang"},"change_message_id":"fa4b8c3a6aac176bcf00ddfc8b00eec1c2667c5d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b1bc7bad_c21ecffa","updated":"2023-10-20 03:34:25.000000000","message":"will add a test later.","commit_id":"9d6e73b036ac4f5fee0ea0274c24d60c5b83951f"},{"author":{"_account_id":28691,"name":"Bo Tran","email":"ministry.96.nd@gmail.com","username":"ministry"},"change_message_id":"f8a742a9933c2aee0b41db8488e477e0f3e336e1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"bc87535e_931b88cf","updated":"2023-11-22 02:12:05.000000000","message":"Sorry. I think this patch isn\u0027t need. Because above options can be run with old other version of MariaDB.\n\nIt\u0027s just template, it can\u0027t fit with all version of MariaDB.","commit_id":"fc07d3f2bd1d6bbe2e54225592807d3f8f8baa3b"},{"author":{"_account_id":39300,"name":"Olessya Khussainova","display_name":"Olessya Khussainova","email":"olessya.khussainova@ps.kz","username":"Cellofun"},"change_message_id":"d285d1469945f0634bc0cd89471024f8a005fa47","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"3259f9ff_a5cce289","updated":"2026-09-21 11:16:04.000000000","message":"I checked these parameters with the MariaDB 11.4 and 11.8 images currently supported by Trove. Each parameter was added to the [mysqld] section and checked with the native MariaDB parser:\n\n```mariadbd --defaults-file\u003d/tmp/test.cnf --verbose --help```\n\n`character_set_connection`, `character_set_database`, `character_set_results`, `collation_connection`, and `collation_database` were rejected as unknown variables by both versions.\n\n`character_set_client` was accepted, but MariaDB interpreted it as `character-set-client-handshake`. Setting `character_set_client\u003dutf8mb4` resulted in `character-set-client-handshake\u003dTRUE` instead of changing the client character set. As a control, `character_set_server\u003dutf8mb4` was accepted and an intentionally invalid option was rejected.","commit_id":"ff8c50e15f764115400cebecf08461b55ac05aee"},{"author":{"_account_id":36080,"name":"Erkin Mussurmankulov","display_name":"Eric","email":"erkin.mussurmankulov@ps.kz","username":"mongoose404","status":"PS Cloud services employee"},"change_message_id":"fcc852512aa814870f962eb8da55aa7a8acc03c2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"fb049753_38ee4d8a","updated":"2026-09-21 14:00:22.000000000","message":"LGTM. Thank you for the contribution.\n\nReply to Bo\u0027s comment: even if these options are supported by older versions of MariaDB, we should implement separate validation rules for older versions as a separate task. Each cloud provider is also free to implement their own validation rules.\n\nMy point of view is that we should not tolerate broken functionality in master for aligning with old legacy, unsupported datastores. We also plan to decouple datastores from the Trove core and support as many database versions as possible.","commit_id":"ff8c50e15f764115400cebecf08461b55ac05aee"}]}
