Transfer_bad_PLSQL_into_good_HROUG23.pdf
•
0 likes•47 views
HrOUG 2023, Rovinj, 18 October 2023 Bad examples about PL/SQL and make it better. Best Practice.
Recommended
More Related Content
Similar to Transfer_bad_PLSQL_into_good_HROUG23.pdf
Similar to Transfer_bad_PLSQL_into_good_HROUG23.pdf (20)
Recently uploaded
Recently uploaded (20)
Transfer_bad_PLSQL_into_good_HROUG23.pdf
- 1. Transfer bad PL/SQL into good
- 2. Maik Becker Alexandra Welzel
- 3. Where are we from?
- 5. Unused or unnecessary code
- 6. Unused or unnecessary code
- 7. Unused or unnecessary code
- 8. Unused or unnecessary code
- 9. Unused or unnecessary code
- 10. Unused or unnecessary code
- 11. Unused or unnecessary code
- 12. Unused or unnecessary code FUNCTION next_store_seq RETURN NUMBER IS next_id NUMBER; BEGIN SELECT TRUNC (DBMS_RANDOM.VALUE (1000, 9999)) * bit_shift + cbo_datastore_seq.NEXTVAL INTO next_id FROM DUAL; RETURN next_id; END next_store_seq; FUNCTION next_store_seq RETURN NUMBER IS BEGIN RETURN TRUNC (DBMS_RANDOM.VALUE (1000, 9999)) * bit_shift + cbo_datastore_seq.NEXTVAL; END next_store_seq;
- 13. Unused or unnecessary code
- 14. Unused or unnecessary code
- 49. SQL Statement Syntax Check Semantic Check Shared Pool Check Optimization Row Source Generation Execution Generation of multiple execution plans Generation of query plan Potential Performance Issues
- 51. SQL Statement Syntax Check Semantic Check Shared Pool Check Optimization Row Source Generation Execution Generation of multiple execution plans Generation of query plan Potential Performance Issues
- 53. SQL Statement Syntax Check Semantic Check Shared Pool Check Optimization Row Source Generation Execution Generation of multiple execution plans Generation of query plan Potential Performance Issues
- 57. PL/SQL and APEX
- 58. PL/SQL and APEX
- 59. PL/SQL and APEX
- 60. PL/SQL and APEX
- 61. PL/SQL and APEX
- 62. PL/SQL and APEX
- 63. PL/SQL and APEX
- 64. PL/SQL and APEX
- 65. PL/SQL and APEX
- 66. PL/SQL and APEX
- 67. Maik Becker Alexandra Welzel