Recent content by AndreyB

Thanks. But if I don't have access to the procedure code and therefore cannot modify procedure parameter definition. How should I proceed? I bet there should be some other way or at least some enhancement in incoming DOA version to work around of such a problem.

I have a stored procedure with PLSQL Table as a parameter; type BigInt_Tab is table of number(20); procedure test(AParam in BigInt_Tab); In Delphi to call that procedure: Query.SQL.Text := 'begin test(:AParam); end;' Because in Delphi I cannot use Integer or Float type to store that big...

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...

This is what I found in technet OCI forum ----------------------- When you select a column object you are fetching the object by ‘value’. The lifetime of these objects in the cache is under the control of the application. The object cache has no way of knowing when the application is done using...

We are using Object view wich is based on the next type: create or replace type Invoice_Type as object ( Invc_Sid NUMBER(20), Sbs_No NUMBER(5), Store_No NUMBER(5), Invc_No NUMBER(10), Invc_Type NUMBER(5), Status...

We're using TOracleQuery which retrieves information from object view which has embedded objects. When 'select value(v) from my_view v' is issued the memory usage does not grow, but if we issue something like that 'select v.* from my_view v' or 'select v.embedded_object from my_view' the all...

Switch from dedicated to Multithreaded server. Users will reuse sessions from the pool.

Why when QBESQL is generated the string fields are treated differently than all others? I mean for other types you declare variables and assign values to them, for string fields the clause "field = 'qbe_value'" or "field like 'qbe_value'" is generated. That leads to very unefficient reparsing...

Uncheck Integrated Debugger or switch to Oracle 8.1.7 it seems they fixed the problem.

Surf DOA help for "PL/SQL tables" keyword. There is the complete example for you.

Set QueryAllRecords to false.

I've discovered very interesting problem during massive array insert in TOracleQuery. I have query variable as array of variant and between execution I could change its size (like at first execute it was 10 elements and at the second only one). Sometimes different errors generated like "access...

It has numbers and floats. Check the Oracle datatypes in documentation.

Guess you should declare :seq variable as otSubst and assign it 'you_seq_name.nextval' value.

Excuse me, guys. Are you gonna fix this or not? It's actually a very big problem, may be hidden for some apps for a while. And I believe this is one of the problem of hard to catch unstability when you use DOA in multiple threads.