In today’s video we demonstrate using expressions in initialization parameters, introduced in Oracle database 21c.
The video is based on this article.
The star of today’s video is Deiby Gómez, who is a fellow Oracle ACE Director, and was kind enough to take me sightseeing when I visited Guatemala for a conference.
Cheers
Tim…
There has always been that odd conflict between the language you use for SQL versus the language you use for PL/SQL when it comes to expressing what appears to the be the same thing.
PL/SQL: Do want a datatype that contains two elements? Use a RECORD
SQL> declare
2 type MY_EMPS is record (
3 empno number,
4 ename varchar2(10)
5 );
6 begin
7 null;
8 end;
9 /
PL/SQL procedure successfully completed.
SQL: Do want a datatype that contains two elements? Use an OBJECT TYPE
Slow down there….Take a breath. Because if you’ve read the title of this post and you’re already logging on to your 19c database, I need to you STOP. Before you go anywhere, please read this post first.
OK … lets proceed, now that you’re not going to end up with a table you can’t drop!
There’s been a lot of interest in blockchain technology and rather than having to go out and purchase a completely bespoke solution, there has naturally been a lot of interest in being able to simply utilise blockchain technology in the same place where your other business critical data is located, namely, an Oracle database!
In today’s video we demonstrate the JSON_TRANSFORM function, introduced in Oracle database 21c.
This video is based on the following article, which has a lot more information and examples than the video does.
I’ve written a bunch of stuff on JSON and ORDS, and there’s a YouTube playlist.
As I write this, the moment you do a browser search for “blockchain”, the last thing you will get a match on is the technology elements. Instead, my results are flooded with hedge funds, short selling, Gamestop and bitcoin. A friend has been sending me messages along the lines of “Is it true Satoshi Nakamoto lives in a mountain cave surrounded by computers and wild yaks?”.
A few days ago Oracle made the official announcement about the release of Oracle database 21c (here). This was a rather late announcement, as the product has been available on Oracle Cloud for over a month, but that’s not the subject of this post.
With each new release I feel the need to write a post like this, so here goes…
“It’s a dead language” people said.
“There’s never anything new” people said.
Happy 2021 everyone! And what better way to start than a cheesy pun to make you groan and already to start looking forward to a better 2022
This post is just a quick one to kick off 2021 because officially I’m still on Christmas holidays. I had a question come in regarding the cool SQL Macro features in 19c and beyond. A SQL Macro generates SQL or a SQL fragment as an output from a special PL/SQL function, and most of the demo code you will see in the documentation or on the interwebs returns a SQL macro as a varchar2.
But what if your SQL statement is really large? You might see this
Recent comments
3 years 4 weeks ago
3 years 16 weeks ago
3 years 21 weeks ago
3 years 21 weeks ago
3 years 26 weeks ago
3 years 47 weeks ago
4 years 15 weeks ago
4 years 45 weeks ago
5 years 29 weeks ago
5 years 30 weeks ago