SQLServer2005LimitHandler throws "string out of range -1" error
Activity
Steve Ebersole October 28, 2015 at 3:25 AM
As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.
Steve Ebersole October 27, 2015 at 7:15 PM
This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.
For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/
Daan de Wit January 30, 2014 at 2:08 PM
Just been bitten by this bug as well. Searching should be regex-based so any whitespace is taken into account, not only spaces.
select fielda,fieldb
from table....
causes shallowIndexOfWord method at line 256 to raise string index out of range -1 error. Because it searches with ' 'search' '.
Please find attached debug session.