MySQL Forums
Forum List  »  Stored Procedures

Re: Oracle procedure to MySQL procedure
Posted by: Rick James
Date: July 18, 2014 11:56AM

nextval() -- smells like something to do with SEQUENCEs? Did you convert them to AUTO_INCREMENTs? Or simulate SEQUENCEs? 99% of SEQUENCEs can be converted to AUTO_INCREMENTs, but the schema _and_ code changes necessary are 'impossible' to automate.

What does truncate() do?

The SELECT with LIMIT 1 has no ORDER BY -- which random one row do you want to get?

Consider using @v_something in _some_ of the places where you are declaring v_something.

I see a COMMIT, but no START TRANSACTION.

What does EXCEPTION do? Keep in mind that MySQL does not have all the richness that Oracle has in exception handling.

Bottom line: automatic conversion is probably not practical, nor safe. Plan on learning the details of MySQL.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Oracle procedure to MySQL procedure
1224
July 18, 2014 11:56AM


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.