[MDEV-19035] Make MariaDB Connector/C handle my.cnf parsing for clients Created: 2019-03-24  Updated: 2021-08-05

Status: Open
Project: MariaDB Server
Component/s: Configuration, Scripts & Clients
Fix Version/s: None

Type: Task Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by CONC-394 Some TLS-related options are not sett... Closed
is blocked by CONC-395 Dashes and underscores are not interc... Closed
is blocked by CONC-396 !includedir in my.cnf does not includ... Open
is blocked by CONC-399 Add option that corresponds to --defa... Open
is blocked by CONC-404 Add option that corresponds to --defa... Open
is blocked by CONC-415 Option prefixes not supported in my.cnf Open
is blocked by CONC-416 On Windows, C/C looks for first my.cn... Closed
Relates
relates to MDEV-9055 replace libmysqlclient with Connector/C Open
relates to MDEV-9293 change clients to use Connector/C Closed

 Description   

Client tools like "mysql" use MariaDB Connector/C in 10.2 and above after MDEV-9293. However, the client tools still use the server code to parse my.cnf and other option/configuration files. See here:

https://github.com/MariaDB/server/blob/c0ba036b774b8e35567dccce421890d2199f30ce/client/mysql.cc#L1176

https://github.com/MariaDB/server/blob/c0ba036b774b8e35567dccce421890d2199f30ce/include/my_default.h#L50

https://github.com/MariaDB/server/blob/c0ba036b774b8e35567dccce421890d2199f30ce/mysys/my_default.c#L464

Do we want to make MariaDB Connector/C handle this job for clients at some point too?

 Comments   
Comment by Vladislav Vaintroub [ 2019-06-01 ]

in my opinion, C/C has no business in my.cnf and my.ini
C/C is collection of APIs, designed for database access. There is mysql_option() to control the behavior, and this should be enough for an API.

Do we want C/C to handle command line, and INI parsing for the server? Probably not

Comment by Ian Gilfillan [ 2021-08-05 ]

Can this be closed as wontfix?

Generated at Thu Feb 08 08:48:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.