Skip encoding params for explain query

[albertyw]

Fixes #819
Reverts #798 , #807

@glennmatthews the _explain_query switched from using the raw params to string params as of #798 . Since the params here are only used for executing the query and are not later saved to a DB like in execute_sql, I'm not sure why params needed to be force_stred? As in #819, some database fields are binary and either cannot be decoded (fixed in the try/catch) or should not be decoded even if they can be decoded.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.15%. Comparing base (23a8da2) to head (a11d58c).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #821      +/-   ##
==========================================
+ Coverage   87.04%   87.15%   +0.10%     
==========================================
  Files          53       53              
  Lines        2169     2164       -5     
==========================================
- Hits         1888     1886       -2     
+ Misses        281      278       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[glennmatthews]

It might be that these lines are actually the part that's problematic for non-UTF-8 data? Looking at #798 and specifically the initial commit of 584a6e2, it was wrapping all three lines here in the try/except at first.

[albertyw]

Looking at #819 , the error people are getting seem to be an error from the postgresql database itself. That would only happen in the cur.execute() so the exception happens before these two lines are even reached.

[albertyw]

Merging this in given the confirmation from #819 (comment)