Skip to main content

A new name - and amazing new future - for PL/SQL

Note: You might think that this was published on April 2nd, but in fact it was published on April 1st.

PL/SQL, the database programming language from Oracle, introduced in 1991 and used by millions over the years to implement data APIs and business logic in mission critical applications from which billions of humans benefit daily, is undergoing a radical transformation in order to stay relevant for, and meta-cool to, future generations of developers.

After a careful examination of all modern programming languages and the definitive StackOverflow developer surveys, the PL/SQL development team implemented a super-secret plan (yes, that’s correct, even the Distinguished Product Manager for PL/SQL, Bryn Llewellyn, is unaware of what you are about to read. So don’t bother him about it, OK?).

I am, therefore, inordinately pleased and honored to be the first to announce the following changes for PL/SQL in Oracle Database 20c:
  1. PL/SQL will now be a case-insensitive language. Sort of.
  2. Only lower-case letters will be supported.
  3. All keywords will now be encased within squiggly brackets. 
  4. The name of the language will change to {plsql}. 
  5. SQL statements are replaced by “yo, oracle!” commands.
  6. All procedures and functions are implemented as recursive callback functions executed asynchronously across all Oracle Database instances in all parallel universes available through the Oracle Quantum Universe Cloud Service.
Let’s take a look at how {plsql} differs from PL/SQL.

Here’s “Hello World” in PL/SQL 18c:

BEGIN
   DBMS_OUTPUT.PUT_LINE (‘Hello World’);
EXCEPTION 
   WHEN OTHERS 
   THEN
      NULL;
END;
/

And now in {plsql}:

{begin}
    {'Hello {dbms_output(.)put_line} World’)(call)(home)(et);
    {wotn};
{end};
/

And you won’t recognize it, but you sure will be impressed by what’s happened to “select from dual”.

DECLARE
   l_dummy sys.dual.dummy%TYPE;
BEGIN
   SELECT dummy
     INTO l_dummy
     FROM sys.dual;
END;
/

And now in {plsql}:

{declare}
   l_dummy {yooracle}”What’s the type of dummy in dual?”;
{begin}
   {yooracle}”What’s the value of dummy in dual?”:l_dummy;
{end};
/

For really complicated SQL statements, you might want to switch to the even more flexible and powerful MLC (“machine learning cloud”) mode, demonstrated so ably below:

{begin}
   {ihaveadream}”What’s the running total for all orders placed 
                last month by customers located within a kilometer 
                of their parents?”
   => {oraclevrconsole};
{end};
/

I could go on and on and on and on and on and on and on and on and on and on (Seriously, I could. The Oracle Quantum Universe Cloud Service, while not available in April 2018,  is up and running in 2020. I am using it to spray tachyons backwards and forwards through time, thereby allowing  me to sign up for as many Oracle Public Cloud trials as I want and write this mind-boggling post).

I could even show you an example of a recursive callback function executed asynchronously across all Oracle Database instances in all parallel universes.

But I won’t. I like you too much.

2018 marks the 37th year I am have working with PL/SQL I am proud of the many achievements of Oracle Database developers over those years. And today, on April 1, 2018, I am confident of a “squiggly bright” future for {plsql} over the next 37 years.

Join me for the journey!



Comments

  1. Hello Steven,

    Please, I beg you, don't frighten us with that "callback functions executed asynchronously" feature, as those clever Node.js guys might even take it seriously :) ...

    Cheers and hope to still continue to travel together in the {PL/SQL} journey :)

    Best Regards,
    Iudith

    ReplyDelete
  2. >> billions of humans benefit daily

    Which is even more impressive, taking into account, that it was developed by and for the inhabitants of Aldebaran system :-)

    ReplyDelete
  3. Please dont frighten us with thee confusing notations. Please keep the language as itis.. But atleast u can enhance to include more features like python. thats it.

    ReplyDelete
  4. Hi All ,

    I am a PL/SQL Developer with 4 year`s of experience working in an Insurance Domain Product based company.
    I have gained good knowledge on Insurance Domain and PL/SQL too.
    Kindly suggest me learning and choosing which technology for my next job would be good for my future in long run(As i am planning to get married soon).

    Thanks,
    Best Regards,
    Ganesh Dasari.
    Dasariganesh38@gmail.com

    ReplyDelete
    Replies
    1. If you are planning to get married soon, I would suggest you learn the language of compromise. It's an old one that pre-dates modern computing, but is very pertinent to your future.

      Delete
    2. Excellent idea, Martin!

      I also suggest checking out APEX - Oracle Application Express. Leverage those PL/SQL skills to build websites!

      https://apex.oracle.com

      Delete

Post a Comment

Popular posts from this blog

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

The differences between deterministic and result cache features

 EVERY once in a while, a developer gets in touch with a question like this: I am confused about the exact difference between deterministic and result_cache. Do they have different application use cases? I have used deterministic feature in many functions which retrieve data from some lookup tables. Is it essential to replace these 'deterministic' key words with 'result_cache'?  So I thought I'd write a post about the differences between these two features. But first, let's make sure we all understand what it means for a function to be  deterministic. From Wikipedia : In computer science, a deterministic algorithm is an algorithm which, given a particular input, will always produce the same output, with the underlying machine always passing through the same sequence of states.  Another way of putting this is that a deterministic subprogram (procedure or function) has no side-effects. If you pass a certain set of arguments for the parameters, you will always get

My two favorite APEX 5 features: Regional Display Selector and Cards

We (the over-sized development team for the PL/SQL Challenge - myself and my son, Eli) have been busy creating a new website on top of the PLCH platform (tables and packages): The Oracle Dev Gym! In a few short months (and just a part time involvement by yours truly), we have leveraged Oracle Application Express 5 to create what I think is an elegant, easy-to-use site that our users will absolutely love.  We plan to initially make the Dev Gym available only for current users of PL/SQL Challenge, so we can get feedback from our loyal user base. We will make the necessary adjustments and then offer it for general availability later this year. Anyway, more on that as the date approaches (the date being June 27, the APEX Open Mic Night at Kscope16 , where I will present it to a packed room of APEX experts). What I want to talk about today are two features of APEX that are making me so happy these days: Regional Display Selector and Cards. Regional Display Sel