Devart Forums

thank you very much. I will follow your suggestion.
I consider the support request as closed

Dear sir.
I found a patch that works in my case
I just set the TOraDataSource->DataSet to which DetailTable is connected to NULL at the beginning of the method and I reset it to DetailTable at the end of the method. With the patch the method is fast again. Thus the problem is due to the connection between the TSmartQuery fields and the controls on the user interface.
Nevertheless I think you still have a problem because the difference in behaviour between version 10.2 and version 11.2 is quite awful.
By the way our version of ODAC is 8.0.2. In any case we are going to upgrade the version to the present one (9.4) in the next days (you will receive an order)

we have the following method that is quite fast with oracle 10.2 but becomes very very slow (unusable) if it is used with oracle 11.2.
the line of code where it becomes slow is
DetailTable->Fields->Fields[ i ]->ReadOnly = disabilita;

void __fastcall TConfordi::DisabilitaCampi( bool disabilita )
{
String ls;
//DetailTable is a TSmartQuery
for ( int i = 0; i < DetailTable->FieldCount; i++ )
{
ls = DetailTable->Fields->Fields[ i ]->FieldName.UpperCase();

if ( ( ls != "F_VALID" ) &&
( ls != "DATA_ULTIMA_MODIFICA" ) &&
( ls != "ID_UTENTE" ) &&
( ls!= "DATA_RIENTRO_TINT_PREV" ) &&
( ls!= "COSTO_LAVORAZIONE" ) &&
( ls != "DATA_LAVORAZIONE" ) &&
( ls != "TINTORIA" ) &&
( ls != "DATA_RIENTRO_TINT_PREV1" ) &&
( ls != "COSTO_LAVORAZIONE1" ) &&
( ls != "DATA_LAVORAZIONE1" ) &&
( ls != "TINTORIA1" ) &&
( ls != "DATA_RIENTRO_TINT_PREV2" ) &&
( ls != "COSTO_LAVORAZIONE2" ) &&
( ls!= "DATA_LAVORAZIONE2" ) &&
( ls != "TINTORIA2" ) &&
( ls != "TIPO_LAVORAZIONE1" ) &&
( ls != "TIPO_LAVORAZIONE2" ) &&
( ls != "TIPO_LAVORAZIONE3" ) &&
( ls != "DATA_CONSEGNA" ) &&
( ls != "NO_LABDIP" ) )

DetailTable->Fields->Fields[ i ]->ReadOnly = disabilita;
}
}

I made my tests and now everything seems OK with the version you suggested
thank you very much

I thank you very much I will try asap and I will post the results

[quote="lclclc"]Dear Shalex
You gave me a good suggestion. I tried with the direct connection and it works!!!
But it does not work via Oracle Client. What did I forget to configure in the client?
The Devart version is 6.0.58 and the client is 10.2.0.1. The example is the one you mentioned in your reply.
WE make hundreads of queries and commands on the same db through the same Oracle client and they all work provided no blob is present

Dear Shalex
You gave me a good suggestion. I tried with the direct connection and it works!!!
But it does not work via Oracle Client. What did I forget to configure in the client?
The Devart version is 6.0.58 and the client is 10.2.0.1. The example is the one you mentioned in your replay

we noticed that the example included in the help oraclelob class to insert a lob does not work any more since version 5.7. It worked correctly in version 5.2. it gives the following error ORA-22275: invalid LOB locator specified.
Due to the fact we followed the example, we had to modify the code and create a stored procedure (as proposed in the blob sample) to have the job done.
Can someone tell us if there is a workaround in order to resume the old behaviour
We are using Oracle 10.2.0.4 and Devart 6.0 with VS2010

I was using successfully the following code with version 2.5. The same code does not work any more with version 3.2 and 3.5, i.e. it returns null for DirectoryName and Filname. Is it a bug or a new behaviour?
Thanks

sqlstmt="Select document_Text from document where document_id='0001'"; //document_text is a column of type bfile
localReader=OpenReader(sqlstmt);
if (localReader.HasRows)
{
localReader.Read();
try
{
bfile=localReader.GetOracleBFile(0);
if (!bfile.IsNull)
if (bfile.FileExists)
{
directoryName=bfile.DirectoryName;///now always null
fileName=bfile.FileName;//now always null
}
}
catch(Exception ex)
{
directoryName="";
fileName="";
}
}
localReader.Close();