Re: CALL in stored procedure doesn't work
Thanks for reply, Peter.
I found mistake. There must be "leave loop1;" in place of "leave proc;" in loop.
About bad approach that I'm using. I know this is very bad idea but this is my first experience in designing DB and for the moment when I implemented this I didn't noticed to use MySQL cache... I have few compound views that incorporates all ids(category_id, author_id, user_id and image_id) at the same time for search on broad range of conditions, e.g. "find authors of articles 1 to 50 and the articles must be in categories one of 1,3,6". With this approach authors that hasn't articles will not appear in such views(same for categories and authors). I don't know SQL very well so the easiest way was to add fake author, article, category and appropriate relations. Another approach was to use UNION to concat records in views that haven't been registered in "rel-tables". This operation takes ~5-10ms which is a lot(because query_cache_size was 0). Hope I'll not get in this trap next time.
Subject
Views
Written By
Posted
3426
February 08, 2015 10:13AM
1328
February 08, 2015 03:32PM
Re: CALL in stored procedure doesn't work
1138
February 09, 2015 12:31AM
940
February 09, 2015 09: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.