We have object view defined on object type which contains nested objects (like collections).
When the following SQL is executed
'select value(v) from my_ov v' we do not experience any memory consumption grows, seems like TOracleQuery.FreeFetchedObjects in TOracleQuery.Next method works just fine.
But if we change SQL to 'select v.* from my_ov v' despite the fact that TOracleQuery.FreeFetchedObjects is called upon each Next, and OciObjectFree for the nested objects in TFieldData.FreeObjects returns no error (I checked return value it's always 0) the object cache grows and grows. The only way to free it is to disconnect the session.
Are we hitting the Oracle bug or it's designed behaviour?
DB version 9.0.1.0.1 with the latest patchset.
When the following SQL is executed
'select value(v) from my_ov v' we do not experience any memory consumption grows, seems like TOracleQuery.FreeFetchedObjects in TOracleQuery.Next method works just fine.
But if we change SQL to 'select v.* from my_ov v' despite the fact that TOracleQuery.FreeFetchedObjects is called upon each Next, and OciObjectFree for the nested objects in TFieldData.FreeObjects returns no error (I checked return value it's always 0) the object cache grows and grows. The only way to free it is to disconnect the session.
Are we hitting the Oracle bug or it's designed behaviour?
DB version 9.0.1.0.1 with the latest patchset.
