Re: 11.2 change in direct insert behavior

| Jonathan, sorry for being unclear. The change is with the "values" form,
| as in the mentioned MOS document:

Mladen,

I see that Charles has already responded with a link to Christian's article about append and append_values.
I'm always a little torn about assigning blame to Oracle when someone does something that they're not supposed to, and then find that it breaks. I can imagine a sequence of events like this at Oracle Corp::

1. we need to allow direct path insert for values - let's make the append hint work, no-one will be using it the wrong way
2. complaints of bugs pop up from people who have been using the append hint incorrectly in the past
3. Oracle introduces append_values for people who really need to append values so that they don't have to run two lines of code for one hint.depending on the circumstances where it's used.

-- 
Regards

Jonathan Lewis
http://jonathanlewis.wordpress.com
Oracle Core (Apress 2011)
http://www.apress.com/9781430239543


"Mladen Gogala" <gogala.mladen_at_gmail.com> wrote in message 
news:pan.2012.02.25.23.17.33_at_gmail.com...


| On Sat, 25 Feb 2012 22:48:10 +0000, Jonathan Lewis wrote:

|

| > Are you sure this is a change - as far as I can recall there has always

| > been a TM mode 6 on "insert /*+ append */"

|

|

| INSERT .. VALUES and APPEND HINT

| Version: 10.2.0.4

|