Skip to main content

Scott Spadafore

The Oracle community lost a good friend & colleague this past weekend.

Scott Spadafore was one of the most intelligent developers that I have ever met. I had the pleasure of working with him on the APEX team during my tenure at Oracle. His thoroughness and ability to see a problem from all angles was simply amazing.

He also liked to help people. A lot. Scott had 16,582 posts on the OTN Forum. That's one post a day EVERY day for almost 45 1/2 years. I'll say it again: 1 post a day for almost 45 1/2 years. Simply amazing!

I was often confused with Scott, only because the first 7 letters of our full names are the same. I'd always joke with him about how many e-mails that I'd have to forward to him, as someone thought that I was the one who helped them on the OTN Forums. He'd joke back that he never had to return the favor.

Scott will be missed dearly, and my thoughts are with his friend & family during this difficult time.

In an effort to consolidate comments, please post them on Joel Kallman's blog entry about Scott, which can be found here: http://joelkallman.blogspot.com/2010/03/scott-spadafore.html

Comments

Bharat said…
He will be missed

Bharat
Andeberhan said…
I am using ms access 2003 to manage all pharmaceutical distribution in the public sector in eritrea. Now I want to migrate to oracle 11g. Is it possible, what are the requirements I need. What basic training course can I suggest to my immediate boss to allow me to take that course.

Popular posts from this blog

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid.  After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry.  This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely?

I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu.  Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user.

To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter.  Any PL/SQL code entered in this region will be executed before any other APEX-related process.  Thus, it is literally the first place that a developer can interact with an APEX page…

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon...

Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure.

Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a format…

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility.While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region.In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can remain un…