not need anymore dataset ApplyUpdates method ??
Moderators: gto, cipto_kh, EgonHugeist
not need anymore dataset ApplyUpdates method ??
We need ApplyUpdates after Post for commit data ( ZConnection AutoCommit properties is true and dataset in insert or edit state ) in older versions. Now not need it. Becouse data commited after post . this is a bug or normal behavior ?
-
mdaems
- Zeos Project Manager
- Posts: 2766
- Joined: 20.09.2005, 15:28
- Location: Brussels, Belgium
- Contact:
If Autocommit is true this means you want to commit after each statement. If not you should set it to false.
The moment you post depends on the CachedUpdates property. When true you have to 'ApplyUpdates' manually. When false the data is posted (and committed with autocommit) immediately.
At least, this is what should happen. If it's not like this it's a bug.
Mark
The moment you post depends on the CachedUpdates property. When true you have to 'ApplyUpdates' manually. When false the data is posted (and committed with autocommit) immediately.
At least, this is what should happen. If it's not like this it's a bug.
Mark
-
bangfauzan
- Senior Boarder
- Posts: 50
- Joined: 31.08.2006, 10:41
- Contact:
Mark is right, autocommit is intended to immediately commit after each statement, regarding ExecSQL or Executed (TSQLProcessor). So it's not a bug.
If we are talking about inserting, editing or deleting data in dataset, ApplyUpdates is required only if CachedUpdates is True, regardless AutoCommit is True or False.
If we are talking about inserting, editing or deleting data in dataset, ApplyUpdates is required only if CachedUpdates is True, regardless AutoCommit is True or False.