Skip to main content

Welcome, Connor McDonald, to the Oracle Developer Advocates team!

I am very pleased to announce that as of 15 June 2015, Connor McDonald, ACE Director extraordinaire, recognized worldwide for both his depth of knowledge on Oracle Database and his excellent presentations, is now an Oracle Developer Advocate for SQL.

Welcome, Connor!

Connor McDonald has, over the past 18 years, worked with Oracle Database systems in Australia, the UK, Southeast Asia, Europe, and the United States. 

He has co-authored three books, and has been a popular speaker at Oracle conferences around the world, specializing in topics on the database engine, in particular SQL and PL/SQL. He has twice won the Inspirational Speaker award by the UK Oracle User Group in 2009 and 2011.  Whether speaking in a full day seminar to a room of developers, or just a "Hey, check out this cool feature" to the person sitting next to him, Connor has always loved sharing information about technology with others.  

While working for clients over the years, Connor realized that the most satisfying part of his job was seeing others grow and develop their skills in Oracle Database technology, helping them discover the amazing things of which the database engine is capable: so much more that simply the place where the bits and bytes are stored.  

When Connor saw the Oracle Developer Advocate team being formed, he asked himself: "So why not take this to the next logical step, and accomplish the same thing on a larger scale?"

Fortunately for Oracle and the Oracle Database user community, Connor answered that question with: "Yes, why not? Let's do it!" To which I agreed with great enthusiasm.

I greatly look forward to the presentations, videos, quizzes, trainings and more that Connor will be unleashing upon the world. 

As many of you likely know, Connor is tucked away in Perth, Australia, so if you are coming to Oracle Open World, be sure to take advantage of the opportunity to congratulate him in person. I sure will!

You can reach/follow Connor as follows:

Twitter: @connor_mc_d


  1. \o/

    Can't be too many advocating Yes SQL! :-)

    Good luck, Connor ;-)


Post a Comment

Popular posts from this blog

Get rid of mutating table trigger errors with the compound trigger

When something mutates, it is changing. Something that is changing is hard to analyze and to quantify. A mutating table error (ORA-04091) occurs when a row-level trigger tries to examine or change a table that is already undergoing change (via an INSERT, UPDATE, or DELETE statement). In particular, this error occurs when a row-level trigger attempts to read or write the table from which the trigger was fired. Fortunately, the same restriction does not apply in statement-level triggers. In this post, I demonstrate the kind of scenario that will result in an ORA-04091 errors. I then show the "traditional" solution, using a collection defined in a package. Then I demonstrate how to use the compound trigger, added in Oracle Database 11g Release1,  to solve the problem much more simply. All the code shown in this example may be found in this LiveSQL script . How to Get a Mutating Table Error I need to implement this rule on my employees table: Your new salary cannot be mo

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,

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