Skip to main content

European Union Mandates All Business Logic in Database by 2020

DatelineDB: April 1st 2019

The European Union turned heads today with a surprise announcement:
Starting 1 January 2020, all business logic in applications must be made available via code stored inside the database. While we recommend that you use Oracle Database and PL/SQL, that will not be required.
This position was apparently taken after close review of the groundbreaking research conducted by Toon Koppelaars of Oracle Corporation, in which he showed that by putting business logic in the database, the overall work - and therefore energy consumption - of the application is reduced, sometimes by as much as 235%. While improving the overall performance of the application by 500%.

A close confidant of the President of the European Union told DatelineDB that the EU would soon adopt a resolution stating that we are now in a climate emergency and every effort must be made in every aspect of human activity to slow down the warming of our planet.

"So the decision to require business logic in the database was basically a no-brainer. A win-win for the customer and the planet."

There are rumors that Java developers all over the world are seeking therapy to deal with their years of falsely implanted memories that made them think the database should be used as nothing but a bit bucket.

And in an unprecedented show of unity, all the JavaScript developers in the world announced that they would henceforth only write code in the dark web, because they really don't like databases. And they are building a new framework: darkDB.js

"Don't worry about that," Brendan Each told DatelineDB. "For a whole boatload of JavaScript programmers that just means they are going to run their editors in dark mode. Shhhhhhh. Don't tell them that's not the dark web."

Larry Ellison was not available for comment.

But Prime Minister May of the United Kingdom did further shock all concerned by issuing her own statement:
Now that the EU has shown such great wisdom and concern for life on this planet, I have instructed my ministers to halt all work on Brexit and instead participate fully in this critical EU initiative, titled For All a Beautiful Database.
If anyone has any questions about putting their business logic in the database, Toon Koppelaars will be available live to answer your questions on May 21.










Labels:

Comments

  1. Uzeyir SuleymanovApril 2, 2019 at 1:20 AM

    I believe this is a April 1st joke, isn't it ? :)

    ReplyDelete
  2. Denis SavenkoApril 3, 2019 at 2:03 AM

    A nice April 1st one)

    ReplyDelete
  3. iudithApril 3, 2019 at 1:11 PM

    After the BREXIT, UK will not have to conform any more to the UE decisions, will it ?
    Now seriously ... probably many UK citizens would really prefer the whole BREXIT to be no more than an April 1 joke ...

    ReplyDelete
  4. AnonymousApril 3, 2019 at 4:23 PM

    ha ha ha
    good one

    ReplyDelete

Post a Comment

Popular posts from this blog

Why DBMS_OUTPUT.PUT_LINE should not be in your application code

A database developer recently came across my  Bulletproof PL/SQL  presentation, which includes this slide. That first item in the list caught his attention: Never put calls to DBMS_OUTPUT.PUT_LINE in your application code. So he sent me an email asking why I would say that. Well, I suppose that is the problem with publishing slide decks. All the explanatory verbiage is missing. I suppose maybe I should do a video. :-) But in the meantime, allow me to explain. First, what does DBMS_OUTPUT.PUT_LINE do? It writes text out to a buffer, and when your current PL/SQL block terminates, the buffer is displayed on your screen. [Note: there can be more to it than that. For example, you could in your own code call DBMS_OUTPUT.GET_LINE(S) to get the contents of the buffer and do something with it, but I will keep things simple right now.] Second, if I am telling you not to use this built-in, how could text from your program be displayed on your screen? Not without a lot o...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

PL/SQL 101: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more