Asking help for insert anydataset(CLOB type) into anydataset col please.

Question

I am using anydataset as a column type. after referring to the demo anydset.sql:
can run then following correctly:
declare
as1 Sys.AnyDataSet;
at1 Sys.AnyType ;
cl1 clob ;
begin
Sys.AnyDataSet.BeginCreate(DBMS_TYPES.TYPECODE_CLOB,at1,as1);
for i in 1..2 loop
     as1.AddInstance();
     cl1 := to_clob(rpad('Clob',i*10,'Clob')) ;
     as1.SetClob(cl1) ;
end loop ;
as1.EndCreate();
--anydataset_display_value(as1);
end ;
while if just added one sql to update the cell value to as1 as following:
declare
as1 Sys.AnyDataSet;
at1 Sys.AnyType ;
cl1 clob ;
begin
Sys.AnyDataSet.BeginCreate(DBMS_TYPES.TYPECODE_CLOB,at1,as1);
for i in 1..2 loop
     as1.AddInstance();
     cl1 := to_clob(rpad('Clob',i*10,'Clob')) ;
     as1.SetClob(cl1) ;
end loop ;
as1.EndCreate();
--anydataset_display_value(as1);
update dumatmp.tbad set colanydataset1 = as1 where id = 0;
end ;
I got :
ERROR at line 1:
ORA-22370: incorrect usage of method AnyData Insert
ORA-06512: at line 14
why? I know that we did not support embedded LOBs in anydata, is it the same for anydataset and documented?
Thanks a lot, hope can got response asap, happy Christmas!

Answer 1

Also, you should always close your resources in finally blocks. So not this:
try {
  st.executeUpdate(query);
  st.close();
} catch (SQLException ex) {
  Logger.getLogger(Parqueadero.class.getName()).log(Level.SEVERE, null, ex);
}because if executeUpdate throws an exception, the close() method is not called. Do this instead:
try {
  st.executeUpdate(query);
} catch (SQLException ex) {
  Logger.getLogger(Parqueadero.class.getName()).log(Level.SEVERE, null, ex);
} finally {
  st.close();
}That way the close method is always called no matter what happens.
I'm also a bit confused by a method which closes a resource which it didn't create. The general rule of thumb is that if you (some piece of code) create a resource, you should also close it. But your statement object is being created by a static method from some other class. For all I know that could be getting a statement from a "statement pool" of some kind and you shouldn't be closing it in this method.
Of course there are plenty of exceptions to that rule of thumb, but I'm not convinced that this code is one of them.
And it is completely normal for new programmers to finish a project and then immediately want to improve it by rewriting and redesigning. And that's not limited to new programmers, either. Management advice of the form "Be prepared to throw away the first version" dates back at least to the 1970's. However, you should beware of the "second system effect" which is described in [The Mythical Man-Month|http://en.wikipedia.org/wiki/The_Mythical_Man-Month].