Overhead of using java.sql.STRUCT

Question

I am calling a stored proc passing in a java.sql.STRUCT
created via DDL statement
CREATE TYPE APPDBA.MY_STRUCT
AS OBJECT
USER_KEY INTEGER,
USER_HOME VARCHAR2(32)
My question is:
when i am creating a structdescriptor from java
oracle.sql.StructDescriptor sDesc =
oracle.sql.StructDescriptor.createDescriptor ("APPDBA.MY_STRUCT", mConnection)
what exactly goes on under the hood here? Does the driver
make a round trip call to the DB every time?
Does it do some sort of caching?
Thanks.

Answer 1

Thanks for your reply. But please take a look at the following code snippet. It intends to add a Timestamp representing the
start of a day (time component 00:00:00) to a time component (having Date to 01-01-1970):
        Time time = new Time(61952000);
        Calendar c = Calendar.getInstance();
        System.out.println("time: " + time); // 18:12:32
        c.set(Calendar.HOUR_OF_DAY, 0);
        c.set(Calendar.SECOND, 0);
        c.set(Calendar.MINUTE, 0);
        c.set(Calendar.MILLISECOND, 0);
        System.out.println("date: " + c.getTime()); // Fri Apr 03 00:00:00 CEST 2009
        Timestamp timestamp = new Timestamp( c.getTimeInMillis() + time.getTime() );
        Date d = new Date(timestamp.getTime() );
        System.out.println("\nresult: " + d); // result: Fri Apr 03 17:12:32 CEST 2009If I assume that getting and setting the milis always deals with timezone independent values, but operating methods
like toString(), getHour() etc use the timezone, then I can not explain the result (last line): 17:12:32 is the timezone
independend value. Should'nt d.toString() show the timezone dependend value of 18:12:32?