[MXS-3021] Allow dbfwfilter to be less strict Created: 2020-06-04 Updated: 2020-06-05 Resolved: 2020-06-04 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | dbfwfilter |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.10 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
When the dbfwfilter is just used to make sure developers don't accidentally drop databases, the refusal to route multi-statement queries and unknown SQL is too limiting. Making the behavior configurable would allow the user to control how the filter behaves in these cases. |
| Comments |
| Comment by markus makela [ 2020-06-04 ] |
|
Added the new strict parameter that can be set to false to allow currently unsupported SQL to be routed. |