aborting the transaction by setting a feedback message_type should be more explicit
Bug #101113 reported by
Jan-Wijbrand Kolman
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Silva |
Fix Released
|
Wishlist
|
Jan-Wijbrand Kolman |
Bug Description
why on earth there is a *REMOVE* button.
JW wrote:
Currently, when providing user feedback where the
message_type is set to 'error', the whole ZODB transaction
is aborted.
I think there should be a seperate explicit message type for
this ("abort"?), since sometimes you do want the transaction
commited, but still provide some warning signals to the end
user.
BTW, for the Silva-1.0 branch the security declaration was
corrected (by GuidoW), but for the 0.9.3 branch it is still
wrong...
Changed in silva: | |
importance: | High → Wishlist |
Changed in silva: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Well, in my eyes an error is an error. And if there is an
error nothing should be saved.
You still can use "warning" for notifications.
The problem with making it explicit is, that you, as a UI
developer, have to think about it. I don't think UI
developers should think about a database rollback.
Just my 2 cents.