In previous posts about caching mechanism of determinstic functions I wrote that cached results are kept only between fetch calls, but there is one exception from this rule: if all function parameters are literals, cached result will not be flushed every fetch call.
Little example with difference:
It’s possible to get an error after granting privileges to an external file system. One of those errors is tedious to resolve until you understand the rules governing Java NIO file permissions.
You grant privileges to external file systems as the
sys user with the
grant_permission procedure of the
dbms_java package, like
x ^ y = y ^ x.
(x ^ y) ^ z = x ^ (y ^ z).
x ^ (x v y) = x.
x v y = y v x.
(x v y) v z = x v (y v z).
x v (x ^ y) = x.
Joins appear (to me) to be getting a lot of bad press recently. In discussions I’ve had and articles I’ve read many give the position that joins are somehow inherently bad and to be avoided at all costs.
I’ve never been entirely convinced by the “joins are bad” arguments however. Partly because there’s few concrete cases actually demonstrating the (additional) cost of joins. Instead discussions tend to be hand-wavy arguments around extra CPU cycles used or something to that effect.
On March 17, 2014, I became an employee of Oracle Corporation for the second time. My first round with Oracle started in August 1987. My second son, Eli, was less than a year old. I'd been incredibly bored with my consulting gig, which consisted of babysitting a reporting system on a DEC10 "mainframe", based on a flat-file database – but a database.
So I checked the Help Wanted pages (no Internet, no smartphones, no LinkedIn) and came across an ad from Oracle Corporation. It contained the word "database", so I figured: "Why ?"
The following update forms the basis of a DIY connection pool. It is intended to allocate an unused session to whoever requests it:
Always looking for ways to increase the entertainment value of the site, I came up with this idea last night.
You have thirty seconds to answer ten true-false questions.
With the clock on the page counting down, you are shown a statement about PL/SQL and you must quickly decide: true or false.
Of course, the same could be done with SQL, APEX, etc.
Thanks to all folks who attended Oracle 12c Multitenant workshop in Bangalore. It was really a great session and well received by all the participants. I appreciate all your interests to know about Multitenant, play with the new architecture and explore the changes. Few points to make note from this event – 1.
Back on the films today, here’s another six to get:
It always happens when I’m in a hurry. Yes, I ran into one of those pesky little features with Oracle’s
DBMS_JAVA package. While I try to write entries with proper GeSHi case semantics, like everyone else I tend to write PL/SQL initially in lowercase. That led me to the discovery of this wonderful error message: