My latest iteration of critical
best practices for PL/SQL, this class covers four main
topics:
- Unit test your PL/SQL
code. I offer "six simple steps to unit testing
happiness", based on test-driven development principles.
I then show how to implement these steps using Qute, the
Quick Unit Test Engine (www.unit-test.com). It's been a
lot of fun demonstrating Qute to developers on this
tour; it never fails to impress with how easy it is to
construct and run tests. Check it out!
- Optimize SQL in PL/SQL
programs. From BULK COLLECT and FORALL to table APIs, it
is absolutely critical that you both take advantage of
key special features in PL/SQL to execute SQL, and also
control how SQL is written in your applications.
- Manage errors
effectively and consistently. We'd rather not have to
worry about errors being raised in our programs, but
they are going to happen so we have to code for them.
This section reviews many of the nuances of error
management in PL/SQL (have you heard of DBMS_ERRLOG, for
example?) and then offers key best practices.
- Write readable,
maintainable code. Well, sure, of course, don't we all?
PL/SQL is inherently very readable, but there is an
awful lot we can do to make our code even more
transparent and self-documenting.
I encourage you to
download this seminar, along with the
demonstration zip file, and use it to help you improve
the quality of code you write! I will present twice at
ODTUG on June 20 and 21
("Six simple steps to unit testing happiness" and "SQL games
we can play in PL/SQL"). Hope to see you there! |
