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
Comments
Sure, there are some restrictions in there, but I would never recommend using any pre-release application for large-scale production work anyways.
In time, this will correct itself once the production release hits the streets.
Thanks,
- Scott -
I can appreciate the advice on not using beta code in production, but enforcing that restriction so tightly in the license is a little harsh.
I know what you mean, and can't speak for Oracle, but I suspect if they didn't include this, someone, somewhere would trash a production system and try to sue Oracle based on a faulty pre-release product.
While I'm not a lawyer, I suspect you clicking the "I Accept" button makes it hard for Oracle to be liable in such an event.
To be safe, I guess we'll all have to wait for the Production release.
Thanks,
- Scott -