BLK4: Converting from Row-by-Row to Bulk Processing (PL/SQL Channel)

This lesson demonstrates the steps needed to convert from "legacy" code that still relies on row-by-row fetching of data and repeated DMl statement execution, to a FORALL- and BULK COLLECT-driven implementation.

========================================
Practically Perfect PL/SQL with Steven Feuerstein

Copyright © 2015 Oracle and/or its affiliates. Oracle is a registered trademark of Oracle and/or its affiliates. All rights reserved. Other names may be registered trademarks of their respective owners. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the “Materials”). The Materials are provided “as is” without any warranty of any kind, either express or implied, including without limitation warranties or merchantability, fitness for a particular purpose, and non-infringement.

[jinayshah]

Hi Steven - @minute 21.56 in the video, function update_employee. in case of any update failures, you are handling an exception "bulk_error" but how do you ensure that the corresponding insert gets rolled back? You showed a way to communicate the failed employee records from insert_history function to update_employee, but it needs to be done the other way round too ? to ensure "INSERT+ADJUST+UPDATE" is one transaction like in the case of cursor for loop.

[nasimchaklader]

Hi, what is purpose to use this procedure "adj_comp_for_arrays", is it to continue in case any exception on insert_history this procedure?