| Issue Number | 4628 |
|---|---|
| Summary | [Internal] AdHoc Query Returns With Error |
| Created | 2019-06-12 11:17:54 |
| Issue Type | Bug |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2019-06-17 08:40:41 |
| Resolution | Won't Fix |
| Path | /home/bkline/backups/jira/ocecdr/issue.245362 |
Any query using or joining the usr table returns with an error message:
Traceback (most recent call last): File "D:\Inetpub\wwwroot\cgi-bin\cdr\CdrQueries.py", line 14, in <module> cdrQuery.run() File "D:\cdr\Lib\Python\CgiQuery.py", line 32, in run elif self.doWhat == "runQuery" and self.queryText: self.runQuery() File "D:\cdr\Lib\Python\CgiQuery.py", line 160, in runQuery val = cgi.escape(u"%25s" %25 col) or u" " UnicodeDecodeError: 'ascii' codec can't decode byte 0xda in position 0: ordinal not in range(128)
Correction:
It's not every query, only the ones that include the column "hashedpw", i.e.
select *
from audit_trail a
join usr u
where document = NNNN
It has been impossible for the CdrGuest account to read
the usr table ever since CBIIT took over our hosting, years
ago. That's why we created the open_usr view.
After I submitted the ticket I was wondering if that's an issue we had talked about before. However, I don't remember the existence of the open_usr view at all. Maybe I will remember next time and maybe you'll stop reading CDR tickets while on vacation? Most likely neither will happen. 🙂
We don't have control over what CBIIT lets us see in that table.
Elapsed: 0:00:00.001231