22:00 Even in my university projects I always have a separate file with just my sql statements, safely stored into functions, making a little library of database manipulation code. I don't need to change every single line of code, I just change that little database functions library.
bulks are meant for performance. but in the vast majority of use cases, simple and clear code is always a better option, despite the performance drawback.
That's a great point, Zex - as long as the performance drawback doesn't cross a red line for users. So here's how I would rephrase your comment: Software needs to be FAST ENOUGH for users not AS FAST AS POSSIBLE. So don't perform unnecessary optimizations that make your code complex and hard to manage. What do you think? :-)
It is one of the best PL/SQL tutorials I have found in the youtube form the point of view of performance. Can you please create a tutorial on AWR report?
MI was caught in the trap here, it is still unclear to me. Sorry, I started to feel silly. When I executed in Toad it returned Count=4. But still when I read it, I don't get it how it returned 4. Can you elaborate it or can you make an other post on this please. In the function: store_and_return_date --#1. First call to insert into the Collection: dates with parameter's SYSDATE add_date (date_in); IF call_in_plsql_in = 'YES' THEN --#2.Second call to insert into the Collection: dates, with SYSDATE current add_date (SYSDATE); END IF; Since the table: tab has got 4 rows, what impact does it make while calling functions with parameter (call_in_plsql_in=YES/NO).
