Sorry - finally found it explained in the DOA documentation.
"StatementCache" determines if Oracle does cache the statements on the server and thus impacts performance on repeated statements as long as these are in the cache.
One more detail:
is "StatementCache" related to TOracleDataset.ReadBuffer?
(we have TOracleDataset.QueryAllRecords=false and TOracleDataset.ReadBuffer=25)
Which statements are cached with "StatementCache" and does that impact WHEN a post is committed?
For me it is still not clear how "StatementCache" works here and what it is used for.
Is it somehow related to TOracleDataset.cachedUpdates?
We have TOracleDataset.commitOnPost=true and TOracleDataset.CountAllRecords=true.
We see severe network performance degregation and now I would like to...
Many thanks Marco!
This did the trick finally.
I have started this "migration" project from Paradox to Oracle actually in 2018 with Delphi 6 and by then these BLOB fields were added to the TOracleDataset as TMemoField.
Removed the Memo fields and added them again to the TOracleDataset...
There is a property "BlobType" and that was "ftOraCLob" (when field was added to the field list of the TOracleDataset.
Changed that to ftWideMemo.
This did not changed the issue.
There is no property "FieldType" or "Type".
Actually, when the DBMemo does have data, we cannot change the record at all. Then we get an error "Record has been changed by another user".
DOA: 4.1.3.5
OCI: D:\ORACLE\app\oracle\product\11.2.0\server\bin\oci.dll
session.ConvertUTF: cuUTF8ToUTF16 (cannot change this - even when...
I am using TOracleDataset with:
SELECT S.ROWID, S.* FROM STAMM S
The table contains 1 NCLOB field that is displayed in in TDBMemo.
As soon as we do
StammTable.Edit;
the text in the TDBMemo gets changed to "??".
When we save with
StammTable.post;
StammTable.session.commit;
it still...
Migrating BDE application I find that there seems to be no "RecordNumber" function equivalent for TOracleDataset.
We look for the position counter of all records read (so far).
E.g the query reads 50 records (RecordNumber is 1), user does click on TDBNavigator-next 3 times and then RecordNumber...