Some time ago, I had to give a fundamentals course on the Oracle SQL language. An important topic within that course is the joining of tables. What I was missing in the course book was a clear demonstration on the differences between the traditional Oracle join syntax and the ANSI SQL join syntax. In this blog post, I’ll make a comparison between the two join syntaxes.
Last week I released version 2.5 of the Select2 APEX plugin in which I introduced the lazy loading feature. I also wrote a blog post that described in what way you had to apply lazy loading to a Select2 page item. The technique involved consisted of creating an On Demand AJAX process that then had to be referenced in the Remote Data Process item setting. The bad thing about this Remote Data Process was that you had to duplicate the query from the item’s LOV definition to successfully return the query result in JSON format. It was a solution that worked, but my instincts told me there had to be a better way to incorporate lazy loading in the Select2 APEX plugin. However, I wasn’t able to come up with a better solution.
A long-requested feature for the Select2 APEX plugin is the ability to lazy load the LOV data. Lazy loading is an AJAX-driven technique that improves page performance by not executing the LOV query until the point at which it is actually needed. This feature can play an important role when dealing with large data sets. Therefore, I am glad to announce that version 2.5 of the Select2 APEX plugin finally includes the lazy loading ability. In this blog post I describe how you can apply lazy loading to a Select2 page item.
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.