Bug #96347 Connector/Python ClientFlag SESION_TRACK is a misspelling
Submitted: 26 Jul 2019 18:34 Modified: 27 Jul 2019 5:53
Reporter: Nicholas Williams Email Updates:
Status: Verified Impact on me:
None 
Category:Connector / Python Severity:S3 (Non-critical)
Version:8.0.17 OS:Any
Assigned to: CPU Architecture:Any

[26 Jul 2019 18:34] Nicholas Williams
Description:
In the Connector/Python class `mysql.connector.constants.ClientFlag`, the `SESION_TRACK` flag constant is a misspelling. It should be `SESSION_TRACK`. Normally, I would say that, for backwards compatibility with those people already using `SESION_TRACK`, both constants should be maintained, and I won't object if that's the route you take, e.g.:

    SESION_TRACK = 1 << 23  # deprecated
    SESSION_TRACK = 1 << 23

However, since nothing else in Connector/Python supports session tracking (nothing calls `mysql_session_track_get_next` or `mysql_session_track_get_first`), I highly doubt anyone is currently using `SESION_TRACK`.

How to repeat:
Read the source code.

Suggested fix:
Fix the spelling.
[27 Jul 2019 5:53] Umesh Shastry
Hello Nicholas,

Thank you for the feedback.

regards,
Umesh