The two things I love most about APEX are its community and the ability to extend it and build new tools around it.Continue reading
Oracle APEX Release 20.2.0.00.20 was released on October 21, 2020. You can find the download on this shortcut link: apex.oracle.com/download/
As you know, from previous posts like https://www.oracle-and-apex.com/differences-between-apex-20-1-and-19-2/, my first task is to see what has changed under the hood, like the metadata repository aka Views and on the API Layer.
And I can tell you, many new and good things are in this release !Continue reading
Oracle APEX 20.1 was finally released on April 23rd 2020 !
As usual, once the download is available, I take a look at the View and API Layer, to see what’s changed there.Continue reading
Oh boy, what happened?
Yesterday I sent an emotional tweet after reviewing a piece of (open source) code, which wasn’t documented well and didn’t include inline comments:
After that I turned away from Twitter, went to sleep, got up again, and had an awesome day with the family. Until I looked at my Twitter responses and mentions.
Here are some examples:
This discussion steered a wrong way and partly painted a wrong picture and wasn’t what I was after.
I WANT comments. I BELIEVE they are good and vital.
Just because some comments are unnecessary or wrong, doesn’t mean you shouldn’t comment at all.
The opposite is true: if you ever stumble across a wrong comment in some code, lets change it. Lets improve it. Lets fix it.
No matter how smart you think you are. No matter how “self explanatory” you think your genius code is. Comments are vital. Comments are there to explain the reasoning behind your (crappy?) code to OTHERS. They might not be as smart as you, they might not have the same information level as you.
Heck, for all we know they might not be #orclAPEX developers at all. I’ve seen Java guys (no offense) tempering with APEX applications. Mostly we see regular database developers, or former Forms developers diving into APEX. They need guidance and a bit more explanation of your “oh so smart code”.
Now get your personal feelings aside and do your job. Properly! And produce the most beautiful code, ever !
P.S.: I know, I know. Life is hard, there is no time. Nobody wants to pay you for extra time. But commenting your code is not extra time. Writing documentation about implementation details is not extra time. It is an essentialPART of software development.
If you are in a job that doesn’t give you the time to comment your code, think of a change.
A few years ago it was deemed state-of-the-art to store any kind of extra resources (images, css/js-files) directly on the webserver.
Of course this was just the best-practice, left with many who were not able to follow because of company restrictions: no access to web server, not allowed to store files, too many regulations, and so on.
Luckily APEX 5++ gave us nicely working Static Application Files and Static Workspace Files. Now everyone is using those to store extra files.
I love to go to Oracle meetings, conferences, trainings, and all that. Why? I actually like my job and I want to get better at it. Also I’m very lazy and always look for shortcuts and easier ways to do things. Continue reading
For my little Webserver Logfile Analysis project I had to solve the problem of how to stream data from a flat file into a relational datamodel in my target database.
Since I used NodeJS in several projects over the past years, it came to my mind at first. On a second thought and by consulting some friends another, easier, solution materialized:
This requirement pops up every now and then, time to put it in a blogpost so I can find it myself again when needed :-)
In various integration scenarios it is required to have users swiftly move between applications written in various technologies. This is very common for legacy Forms applications where some functionality is moved to APEX. From the Forms menu one entry could open a Form, another one an APEX page.
Yesterday I put a question on twitter, to find out what others prefer: table names using singular or plural form. I expected one or two replies, not an avalanche :-)
datamodel question for monday morning: why would you use plural to name a table (ie. USERS)? Isn’t it more accurate to use singular -> USER.
— PeterRaganitsch (@PeterRaganitsch) April 10, 2017