This is an awesome start. Would it be possible to run a test that raises the encoding error so we can verify the reverse circumstance here?

It is hard to catch the error as a specific encoding error. I ended up adding a keyword argumentclient_encoding and raising aValueError ifclient_encoding does not match the database encoding (2nd commit). What do you think?

I ran some more tests and got errors for adapted parameters that do not have theencoding attribute. Therefore I added thehasattr check and the test filtering by a number in the 3rd commit.