The ODTUG Kscope conference always starts with a full day symposium. There are several specialized tracks going on, and I attended the APEX track (mainly).
The room was packed, I would estimate around a 175 delegates.
Joel Kallman started the day with an overview of the history of APEX, including a video of Steve Balmer being very enthousiastic about APEX. He also told a bit about the background and how some features evolved throughout the years, like Themes and lessons learned with the packaged applications.
In the Kscope14 sunday symposium today, Steven Feuerstein explained that MEMBER OF syntax was slow in SQL and fast in PL/SQL. I challenged him that perhaps it was missing indexes on the nested table? My mistake - I got the task of testing it and see if that was the case... So I tested and was surprised at the answer.I'm creating a nested table type and a table with a column of that type and populate it:create type nested_varchar as table of varchar2(100)/
I left to chance where students would attempt to place their external files in a Linux or Unix implementation. As frequently occurs, they choose a location in their
student user’s home directory. Any attempt to read an external table based on a file in this type of directory fails because it’s not accessible by the Oracle user. You can’t simply
chown the directory and files in the directory.
The failure returns the following result:
Steve Ballmer is a terribly oblivious ultra-rich man.
[Interesting to consider how in the US, land of free speech, this nasty brutish fellow is being punished -well he was being punished before Ballmer rewarded him - for his private thoughts. That's pretty awful when you think about it.]
In the last couple of years, I have shifted my attention away from the human condition (wars here and there, cool new gadgets, etc.) to the non-human condition: the natural world of trees, water, creatures large and small, the process of evolution.
A call to a
PRICE_S1 sequence in a query with an
ORDER BY clause is disallowed. Any attempt raises the following exception:
While working with an error that my students surfaced in the Oracle Database 12c, I blogged about the limit of using a subquery in an Oracle
INSERT statement, and I discovered something when retesting it in MySQL. It was a different limitation. I was also surprised when I didn’t find any mention of it through a Google search, but then I may just not have the right keywords.
Sometimes my students find new errors that I’ve never seen. One student did that this week by including an
ORDER BY clause in a subquery that feeds an
INSERT statement. It raises an
ORA-00907 exception, like:
Thursday I went for a quick trip to Nieuwegein for the Amis KScope Preview. Nice evening :-)After a train to Copenhagen and a plane to Amsterdam, I checked in at the CitizenM hotel at Shiphol airport. A bit different hotel - toilet and shower in big glass tubes in the room - but actually fairly nice for a single traveller.
Last week was the annual conference for the Oracle User Group Finland. This time the conference was at the Finnish Nature Center called Haltia. Needless to say that the location was beautiful.