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

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of work, revamping algorithms, ensuring correctness, you know the score. Then my eyes snagge
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

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post. PL/SQL is a strongly-typed language . Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type). PL/SQL offers a wide array of pre-defined data types , both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package). Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types. You can't really declare your own "user-defined" scalars, though you can define subtypes  from those scalars, which can be very helpful from the p
24 comments
Read more