UDPATE: Free APEX Hosing

Well, you get what you pay for. It seems as if there is a single public workspace that you're account will be tied to when you create a free account with AppsHosting. Hardly secure! Any other user is free to wreak havoc on what you build, unless you meticulously lock each and every page. Unfortunately, that won't stop anyone from seeing (and altering) your database objects, as those are all shared among all users as well.

Guess I'll keep the account to use in a bind, but won't ever put anything in there that I don't want anyone else to see or that I may want to see again...

Comments

Unknown said…

Can't you do the same thing on htmldb.oracle.com? Just for development...

May 2, 2007 at 10:07 AM

Scott said…

Yes, you can, but if your application becomes "production ready", you will have to move it elsewhere. Sounds like Appshosting can take what you have and move it to production more seamlessly.

Also, keep in mind that the Oracle service makes no guarantees about its uptime, availability. They *COULD* wipe the entire server clean tomorrow and there's nothing anyone would be able to do about it...

- Scott -

May 2, 2007 at 10:32 AM

Unknown said…

Oracle wouldn't do a thing like that, surely! ;-)

May 2, 2007 at 1:51 PM

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 forma

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 rem

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 p

Scott Spendolini's Blog

Search This Blog