TN-2417 provide ugly workaround to failed query

[pbugni]

Hopefully a temporary workaround, run a second query for the entire json document if the query for the json path field fails.

[pep8speaks]

Hello @pbugni! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file portal/models/questionnaire_response.py:

Line 375:40: E251 unexpected spaces around keyword / parameter equals

[pbugni]

@ivan-c should we include a rollback of yesterdays SQLAlchemy downgrade attempt, as that didn't prove to be the problem?

[ivan-c]

Looks good, thanks for branching from master!

Is there anything else (metadata, system state) we would want to log? Nothing comes to mind, but I'm not sure we'll be able to reproduce with QNR.id only

[ivan-c]

@ivan-c should we include a rollback of yesterdays SQLAlchemy downgrade attempt, as that didn't prove to be the problem?

I'd prefer to minimize change to master until we can figure this out. I'll merge what we have in master into develop and restore Wayne's changes there; they'll become part of the next release.

[pbugni]

@ivan-c should we include a rollback of yesterdays SQLAlchemy downgrade attempt, as that didn't prove to be the problem?

I'd prefer to minimize change to master until we can figure this out. I'll merge what we have in master into develop and restore Wayne's changes there; they'll become part of the next release.

Sure, sounds wise.

[pbugni]

Looks good, thanks for branching from master!

Is there anything else (metadata, system state) we would want to log? Nothing comes to mind, but I'm not sure we'll be able to reproduce with QNR.id only

I really don't know what else to log. We can't reproduce at all, but at least we'll have a pointer to the db row that behaved poorly.