Hi, Marko.
Have another set of wrong behaviour of TOracleDataSets:
1) Delphi documentation states that
But in case when oracle dataset has one inserted and not posted record then
both of EOF and BOF remains true.
Addition check on State of Dataset is a workaround.
2) Next use case doesn't work under cached updates for Master-Detail pair:
2.1) add detail
2.2) delete master.
The problem that Session.ApplyUpdates firstly applies delete actions then inserts/deletes. This is however right behaviour as it prevents errors concerned to nondeferred unique constraints. Guess, better solution is to delete modified/inserted detail records when master is about to delete.
Have another set of wrong behaviour of TOracleDataSets:
1) Delphi documentation states that
(ms-help://embarcadero.rs_xe3/libraries/Data.DB.TDataSet.Eof.html)Tip: If both Eof and Bof are true, the dataset or range is empty.
But in case when oracle dataset has one inserted and not posted record then
both of EOF and BOF remains true.
Addition check on State of Dataset is a workaround.
2) Next use case doesn't work under cached updates for Master-Detail pair:
2.1) add detail
2.2) delete master.
The problem that Session.ApplyUpdates firstly applies delete actions then inserts/deletes. This is however right behaviour as it prevents errors concerned to nondeferred unique constraints. Guess, better solution is to delete modified/inserted detail records when master is about to delete.