Re: Store procedure select fails
Why not just use GUIDs?
If there's a imperative reason you must write a custom sproc for this, given the primitive language and absence of debugging toools with MySQL sprocs, they're a pain. The only debugging method I know is the brute force method of stubs & drivers we learned long ago in school, before fancy debuggers existed. Stub out the controlling values in user variables and track what's happening.
I do see a coding error: x like y returns true only where x exactly equals y, but if you're using the like operator you presumably want x like concat(y,'%'), or x like concat('%',y,'%').
(To preserve text formatting in posted code, use BBCode code tags.)
Subject
Views
Written By
Posted
1412
April 12, 2018 08:00AM
Re: Store procedure select fails
589
April 12, 2018 09:57AM
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.