Skip to main content

New Blog Location

Since I am no longer employed at Oracle, I am going to move my blog to Blogger, thus avoiding any confusion of what I "officially" said about HTML DB and what I "personally" say about it. Please update your bookmarks accordingly:

New Blog Home: http://spendolini.blogspot.com
New Blog RSS: http://feeds.feedburner.com/ScottSpendolinisBlog

Comments

Partha said…
Hi Scott,

Wishing you all the very best for your new assignment. Welcome to Blogger as well :-) Hope to see you write more about HTML DB. Just a note on the blogging - realised that Iam the first person to comment on your blog - It is safe to turn on the Word verification feature of blogger - otherwise you are vulnerable to a lot of spam.

Ok, now that you are relatively free from technical side in the first week, maybe, you can reflect on this: Do you see HTML DB moving slowly towards 'OPEN SOURCE' in the near future? Or wouldn't it be a cool idea to have it as a open source?
Colin said…
Excellent, then you will be 'free' to criticize it for a change... :)

he..he..he..
Scott said…
When it deserves to be criticized, yes, I am free to do so. :)

- Scott -
Scott said…
Do you see HTML DB moving slowly towards 'OPEN SOURCE' in the near future? Or wouldn't it be a cool idea to have it as a open source?
I don't see this happening in the near future, but that doesn't mean it won't. There was some talk of allowing users to create their own HTML DB widgets in PL/SQL, but that's about as close to Open Source as I think the tool will get.

While I believe that OpenSource is an excellent or "cool" idea (love Firefox, T-Bird, Linux, etc.), I just don't see every application going that way in the near term. Maybe our kids or grandkids will laugh at how we all used to pay Oracle or Microsoft for software some day, but I'm not holding my breath...

Thanks,

- Scott -

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…