3. never hard-code an oracle error number.
Published 5 years ago • 5.5K plays • Length 8:13Download video MP4
Download video MP3
Similar videos
-
13:57
get rid of those hard-coded literals! (hc-3)
-
8:00
top nine coding guidelines for oracle pl/sql
-
12:34
hard leetcode sql problem solved (#262)
-
10:16
windows could not start the oracledbconsole on local computer error code 2
-
5:59
5. capture call stack, error code, error stack, error backtrace.
-
13:35
let oracle do the heavy lifting: using compile-time warnings
-
7:51
every varchar2(n) declaration a bug!? (hc-4)
-
12:11
about that error: ora-06502: numeric or value error
-
3:31
1. exceptions raised in declaration section not handled in exception section.
-
2:28
6. always log error (and backtrace) before re-raising the exception.
-
5:03
sql error ora-00942 table or view does not exist in oracle database
-
6:24
valid package with no subprograms you can call?
-
6:43
how not to handle exceptions - part 1
-
17:48
write tiny chunks of (reusable) code
-
6:23
8. use log errors to suppress sql errors at the row level.
-
28:43
mng2: the optimizing compiler of oracle pl/sql (pl/sql channel)
-
2:51
2. an exception raised does not automatically roll back uncommitted changes to tables.
-
7:53
how not to handle exceptions part 2
-
10:22
about that error: pls-00306: wrong number or types of arguments