Bug: updating a view with a CLOB column results in ORA-01461

Question

Here is a database script to create a table and a view:
CREATE TABLE TEST_CLOB(ID NUMBER, TEXT CLOB);
CREATE OR REPLACE VIEW VTEST_CLOB AS
SELECT ID, TEXT FROM
    SELECT ID, TEXT
    FROM TEST_CLOB
    WHERE ID IN (SELECT 1 FROM DUAL)
The following code throws ORA-01461: can bind a LONG value only for insert into a LONG column.
static void Main()
     using (var conn = new OracleConnection(ConnectionString))
          conn.Open();
          var trans = conn.BeginTransaction();
          var cmd = conn.CreateCommand();
          cmd.BindByName = true;
          var p = new OracleParameter("vText", new string('a', 4001));
          cmd.Parameters.Add(p);
          cmd.CommandText = "UPDATE vTEST_ClOB set TEXT = :vText";
          cmd.ExecuteNonQuery();
          trans.Rollback();
Please create a table and a view exactly as shown above.
The error doesn't happen when updating TEST_CLOB table itself or if the view is created as follows:
CREATE OR REPLACE VIEW VTEST_CLOB AS
SELECT ID, TEXT FROM
    SELECT ID, TEXT
    FROM TEST_CLOB
    WHERE ID IN (1)
This code was tested with ODP.NET version 4.112.3.0 and ODP.NET Managed Beta2 version 4.112.3.60.
Oracle 11g Release 11.2.0.2.0 64-bit.
When constructing OracleParameter like this: var p = new OracleParameter(name, stringValue), OracleDbType property is always set to OracleDbType.Varchar2,
but I think it should take into accout the size of the stringValue and change it to OracleDbType.Clob automatically.

Answer 1

I've noticed similar behavior with byte arrays.
Parameters with byte[] data longer than 4000 bytes are treated as RAW or LONG RAW type values (not sure which one exactly).
Explicitly setting parameter type to OracleDbType.Blob works around this problem.
Also, it's very strange that these errors don't seem to occur on tables, only views are affected.
Any thoughts on this please?