Użytkownik Ed Leafe napisał:
>
> No, it's never been troublesome for me. There is ample protection for
> accidental deletion in the UI layer.
>
> With new(), most immediate saves would fail, because no values have
> been entered yet.
>
> So you want to issue a delete(), and not have it actually delete, but
> somehow mark the record for deletion. Then add an additional method called
> "actuallyDelete()" that will delete the marked records?
>
I rather would like that delete works more like new() method, e.g.:
- let's add _deletedRecords attribute (equivalent of _newRecords
attibute in new() method)
- each call of delete() method causes to remove row from dataset
and update _deletedRecords with key of deleted row
- save(), requery() and clear() updates dataset and _deletedRecords,
additionally save() checks _deletedRecords and updates backend
accordingly.
Currently to achieve something similar I need to create local copy of
dataset
and then in beforeSave() update framework dataset and then backend.
--
Regards
Jacek Kałucki
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[email protected]
