Anthony Tuininga

You can use the technique noted in the [documentation](https://python-oracledb.readthedocs.io/en/latest/user_guide/sql_execution.html#fetching-raw-data) to bypass the decode stage and get the raw data. You can then decode it yourself using the "real" encoding --...

Thanks. I think that clinches the fact that you have corrupted data in the database. See my earlier comment about a workaround -- but I would suggest that you correct...

I did some searching and it looks like this issue is due to interpreter shutdown and the fact that in *some* cases, module globals are set to the value `None`...

To be clear: unencrypted .pem for mTLS connections work just fine. The issue is that if the .pem file does *NOT* contain a private key, the code fails -- this...

Looking further into this, I suspect it may be possible to just do this: ```python try: ssl_context.load_cert_chain(pem_file_name, password=params._get_wallet_password()) except ssl.SSLError: pass ``` In other words, try to load the certificate...

Not yet, unfortunately. I'm still waiting but will prod internally again. :-)

I was finally able to test with an older database. When supplying an invalid password for an encrypted PEM file, instead of this error ``` oracledb.exceptions.OperationalError: DPY-6005: cannot connect to...

You're welcome. This will likely become part of 1.1.2, but it depends on a number of factors. You can "watch" this repository -- just for new releases if that is...

I usually add one more comment when the release is made and then close it, but if you prefer to close it now, that's fine, too!

That's a lot of text and I'm not sure what exactly you are trying to say. Can you create a test case that contains the table creation statement, insert statements...