Description
Same situation as reported in this ticket: https://jira.atlassian.com/browse/CONF-10030
It can potentially impact MySQL, PostgreSQL and Oracle.
select review1_.cru_review_id as cru1_16_, review1_.cru_review_type as cru2_16_, review1_.cru_name as cru3_16_, review1_.cru_default_source as cru4_16_, review1_.cru_state as cru5_16_, review1_.cru_description as cru6_16_, review1_.cru_summary as cru7_16_, review1_.cru_allow_reviewer_to_join as cru8_16_, review1_.cru_create_date as cru9_16_, review1_.cru_metrics_version as cru10_16_, review1_.cru_all_reviewers_complete as cru11_16_, review1_.cru_due_date as cru12_16_, review1_.cru_reminder_date as cru13_16_, review1_.cru_issue_key as cru14_16_, review1_.cru_parent_review as cru15_16_, review1_.cru_creator as cru16_16_, review1_.cru_project as cru17_16_ from cru_revpermaid reviewperm0_ inner join cru_review review1_ on reviewperm0_.cru_review_id=review1_.cru_review_id where lower(reviewperm0_.cru_proj_key)='XXX' and reviewperm0_.cru_number=671\G