SELECT * from APEX_MAIL_LOG ORDER BY LAST_UPDATED_ON DESC;
SELECT * from APEX_MAIL_QUEUE ORDER BY LAST_UPDATED_ON DESC;
In the last post I showed how easily you can enable an Interactive Grid for editing, however what if you want to only allow the user to edit certain rows?
Lets imagine a scenario – given the standard EMP table, I should only be able to change the salary of Employees who report to me (i.e. I can’t change the salary of an employee if they report to someone else).
So, let’s create an Interactive Grid with the following query –
Now, for the purposes of this example, given the hierarchy of the EMP table –
I’m going to “pretend” to be BLAKE – since BLAKE is the manager of 5 people.
If you look at the properties of the Interactive Grid you’ll see the “Allowed Row Operations Column” setting, this allows us to define a column in the query which will be used to define whether I can Update…
View original post 125 more words
His blog is a gem :)
Coloring side menu entries
Sometimes you want to add a little more color to the navigation menu. The idea in one project was to use colors for certain areas in an application. The color would show the user where he is currently working. Whether such colors are a feature that end users like, is still part of an ongoing discussion. But here are the technical details how to implement it.
The example uses a very small apex application that I’ll be using for a DOAG2015 presentation “Exotic SQL” (http://syntegris-doag.de/#vortraege).
Steps to create this
I explain the changes in detail a little further down.
- Create a new List template based upon the current one.
- Switch the user interface from the old to the new template
- Edit the template
- Add colors to the parent list entries
- Update alls sub menus to match the parent color
- can be…
View original post 902 more words
10 Oracle SQL features you probably didn’t know
I can not guarantee that you never heared of this. But the majority of developers doesn’t know or doesn’t seem to know. And honestly – most of this information is fairly useless – and mostly harmless.
10. Why we have the CONCAT function
There is a concat function that can be used instead of the concat operator ||.
Nobody uses that! But there is a reason why it exists.
This is from the 8.1.7 Oracle documention
On most platforms, the concatenation operator is two solid vertical bars, as shown in Table 3-3. However, some IBM platforms use broken vertical bars for this operator. When moving SQL script files between systems having different character sets, such as between ASCII and EBCDIC, vertical bars might not be translated into the vertical bar required by the target Oracle environment. Oracle provides the
View original post 2,420 more words