[MXS-39] bugzillaId-731:Boolean configuration parameters accept inconsistent parameters Created: 2015-01-16  Updated: 2015-06-17  Resolved: 2015-04-30

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.0.5
Fix Version/s: 1.1.1

Type: Bug Priority: Minor
Reporter: martin brampton (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

Linux


 Description   

This is imported from bugzilla item: http://bugs.mariadb.com/show_bug.cgi?id=731

Description martin.brampton@skysql.com 2015-02-16 16:20:54 UTC
Where configuration parameters are booleans, there is a widespread assumption that they should permit any of:
1, yes, true, on
or
0, no, false, off
MaxScale software is inconsistent in this respect. It would be better to conform to expectations and support the full range of options.

 Comments   
Comment by markus makela [ 2015-04-30 ]

Changed all atoi calls to config_truth_value where they were used for boolean values.

Comment by Timofey Turenko [ 2015-05-04 ]

checked manually, closing

Comment by Timofey Turenko [ 2015-05-12 ]

verified by playing with different spelling of 'yes' and 'no' enable_root_user parameter (yes, Yes, 1, true, TrUe, No, nO, 0, False).

Generated at Thu Feb 08 03:56:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.