Skip to main content

PL/SQL Now Available for Microsoft Excel, MongoDB, Cassandra and VoltDB!

In a surprise announcement today [April Fool's Day, I now point out on 2 April], Oracle Corporation announced that the PL/SQL language, its (formerly) proprietary database programming language, would now be available as open source on Github.

Simultaneously, Oracle Corporation announced that PL/SQL would now compile and run on MongoDB, Cassandra, VoltDB (as well as the other 256 database products Michael Stonebreaker has helped establish over the last several decades) and, in recognition of the primacy of business analysts the world over, Microsoft Excel.

Bryn Llewellyn, Senior Distracted PL/SQL Product Manager, could not suppress his excitement over these developments: "For years, I've had to content myself with answering questions just from Oracle technologists. Now I can spend all day and all night long answering questions from another 10,000,000 developers. Thanks, Oracle, for making my day."

Steven Feuerstein, TMWKOP (The Man Who Knows Only PL/SQL), was unaccountably glum. He told the San Francisco Chronicle in an interview for this breaking story that "I was perfectly happy with the status quo. We had our tight little community, everyone knew who I was. I felt special. Now?  Now we're just one more open source project that everyone can play with and criticize. What's so great about that?"

For more information, visit www.oracle.com/plsql.

About Oracle

Oracle engineers hardware and software to work together in the cloud and in your data center. For more information about Oracle (NYSE:ORCL), visit www.oracle.com.

About Oracle OpenWorld

Oracle OpenWorld San Francisco is the most important business and technology conference of the year for Oracle customers, prospective customers, and partners. This educational conference is dedicated to helping businesses optimize existing systems and understand upcoming industry trends and breakthroughs driven by technology. Oracle OpenWorld offers more than 2,700 educational sessions, hundreds of demos and hands-on labs, and exhibitions from more than 450 partners and customers from around the world showcasing applications, middleware, database, server and storage systems, industries, management, cloud, and infrastructure solutions—all engineered for innovation. For more information; to register; or to watch Oracle OpenWorld keynotes, sessions, and more, visit www.oracle.com/openworld. Join the Oracle OpenWorld discussion on Twitter, Facebook, and the Oracle OpenWorld blog.



Comments

  1. AnonymousApril 1, 2015 at 1:30 PM

    1st of April :-)? But still I enjoy every Post of You! VERY HELPFULL 4 A YOUNG PROFESSIONAL like me!! Best regards from Germany
    Jonas

    ReplyDelete
  2. Steven FeuersteinApril 1, 2015 at 1:31 PM

    I have been informed by Oracle Legal that I am not permitted to comment on this news until after 1 April.

    :-)

    Glad you enjoyed it!

    ReplyDelete
  3. Steven FeuersteinApril 2, 2015 at 5:25 AM

    And now I can confess to all: this was an April Fool's prank. PL/SQL has not been open sourced. It is still proprietary to Oracle Corporation (though both DB2 and PostgresSQL offer limited support for compilation and execution of PL/SQL code against those databases) and there are no plans - I repeat, NO PLANS - to support PL/SQL on Microsoft Excel.

    :-)

    ReplyDelete
  4. Michael A. RifeApril 16, 2015 at 10:38 AM

    I read your post on Twitter, but did not notice that date of publication. Nice!!

    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

Implicit vs Explicit Cursor: Which should you use?

My post on Conditional Logic in PL/SQL generated some interesting discussion concerning whether to use an implicit cursor (SELECT-INTO) or an explicit cursor (OPEN-FETCH-CLOSE) when fetching a single row of data. "Hmmm," you might be saying to yourself, "a conversation about SQL queries in a post on conditional logic? That's strange." Ah, but maybe not so strange. Because as one person put it in the comments: Yes, this is true. You can use exception handling as a kind of conditional branching logic. But should you? Generally, no. It's a good idea to keep application logic out of exception sections. Developers don't expect or look for business logic in those sections. They are, after all, for dealing with exceptions - errors. So if you put lots of code in EXCEPTION WHEN clauses, they can be easily overlooked, making your code harder to debug and enhance. But that question - and the recommendation to avoid the exception section - then led to ...
16 comments
Read more