Instructions for "Finding the python-oracledb Mode" do not work

[mPyth]

1. What is the link to the documentation section that needs improving?
   https://python-oracledb.readthedocs.io/en/latest/user_guide/tracing.html#finding-the-python-oracledb-mode

2. Describe the confusion
   Operating system: Ubuntu Server 24.04.
   Oracle Instant Client version: 19 (latest of version 19), should run in Thick mode but not sure - that's the reason why this query from mentioned section is run.
   python-oracledb version: 2.5.1
   Remote Oracle database version: "Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production"

   Return value from query (section is "24.2. Finding the python-oracledb Mode") is 'python-o' - the first 8 characters of expected value ("python-oracledb thk : 3.0.0"). Those 8 characters are useless because they are the same for both possible outputs (quotation: "python-oracledb thn : 3.0.0" or "python-oracledb thk : 3.0.0").
   I've tried the same query from my development machine (Windows 10 with SqlDeveloper) and got value 'jdbcthin', also with SqlDeveloper's action "go to declaration" it is possible to see that column "client_driver" is of type VARCHAR2(9) which means there could not be stored more than 9 characters.

3. Suggest changes that would help
   Instead of too long string (example: "python-oracledb thn : 3.0.0") it would be better to insert just one of next two values "thin" or "thick" (or "thn" and "thk" with short version).

[cjbj]

I appreciate you taking the time to report this.

The issue is that your DB version doesn't support the full length. Newer databases do. Arguably we were wrong in deciding not to over-document the limitation of old DBs.

The standard for this column across Oracle drivers is "name : version". By being consistent we make it easier for tools to parse the column.

For your usage, checking Connection.thin and oracledb.version will work. They are also more efficient since they don't require a round trip to the DB.

In summary, I'm not planning to make any change. If your DBAs complain, remind them that 11.2 is so old it only has 'Upgrade Support'.

[mPyth]

Thanks for detailed explanation (especially for Connection.thin workaround).