Working with PL/SQL collections is an important part of the Oracle Database 11g: Advanced PL/SQL exam for which I’m currently studying. This post serves as a refresher on the different types of collections that exist in the wonderful PL/SQL language.
Most development teams have agreed upon some sort of naming convention as it typically increases the readability and comprehension of the source code. Defining these rules is one thing, but correctly and consistently applying them is another. Wouldn’t it be great if we were able to actually validate whether our team-specific naming rules have been applied the right way? Well, I’ve created a package that makes it possible to list all incorrectly named elements in your database schema.
I ran into this mysterious error message while trying to execute a simple Maven Mojo. I call it mysterious because of the fact that the almighty Google couldn’t help me any further on this. Here’s the build log output I had to deal with.
I’m currently in the process of building a Maven plugin to make APEX development even more fun and productive. The primary goal of the Oracle APEX Maven plugin is to streamline and facilitate the build process for APEX applications. That might sound a bit confusing for those of you who are not familiar with Maven or any other build management tool, so let me explain some of the terms I have used so far.
I’m doing a webinar next week for ODTUG about Shaping Your APEX Development Process on Tuesday February 18th at 12:00 PM EST. It’s the first time for me to talk in front of a virtual audience, so it will be kinda special for me. Click here to register for the webinar. I hope to see you there! Well, see is probably not the right word, but you know what I mean. :]
Here’s the abstract of what I’ll be talking about:
Software development with Oracle Application Express is by no means affiliated with enterprise web development. Oracle itself positions APEX as a so-called rapid application development tool, but recommends other products as soon as projects get larger and more complex. I honestly believe, however, that APEX has the potential to cope with these large-scale projects. But – there’s always a but – you need more than just plain APEX.
Last week I was struggling to get the APEXExport utility to work. I was messing around with environment variables, different Java versions, and ugly bash syntax while constantly getting the exact same error message. Anyway, after some frustrating moments, I decided to start all over again and then I came up with a solution pretty fast. Here’s my way to quickly get the APEXExport command-line utility to function properly.