Re: Unpredictable results from stored procedure
> It's not possible in my project to replace LIKE and REGEXP with =
?!? None of the data values your code applies Like to contain wildcard chars; in such cases, Like is equivalent to =, ie use of RLike here is incoherent. Likewise none of the data values the code applies RegExp to have Regex chars, so again RegExp is equivalent to =, ie use of RegExp here is incoherent.
I can't reproduce your problem NULL results in MySQL 5.6, so I've no idea whether the problem arises from your incorrect use of RLike and RegExp, or from a 5.0 bug. If changing those operators to = does not fix the problem, consider upgrading to 5.6.
Subject
Views
Written By
Posted
2436
July 16, 2013 04:09AM
1083
July 16, 2013 11:09AM
1132
July 18, 2013 03:37AM
1145
July 18, 2013 11:59PM
1737
July 23, 2013 01:57AM
Re: Unpredictable results from stored procedure
1242
July 25, 2013 10:35AM
1038
July 29, 2013 04:26AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.