mdipierro wrote:
If you use archive you should not never delete records. You should only have an "active" field and filter out the inavtice ones.
Yes, I realise that :) Further experimentation (while waiting for Gmane to post the message) after I implemented the small patch revealed that the database neatly dropped all archive rows corresponding to the main row, most likely due to a cascading delete. Fair enough that you /should/ not use delete when using archiving, but to get a nasty runtime error? That might surprise the unsuspecting developer who innocently forgets to disable delete functionality. In my app there are lookup tables of codes - activity codes, charge codes and so on - that might be edited during their lifetime. Logic is already in place to prevent their being deleted if they are referenced anywhere, but if they are deleted, I am happy for all archive history to be deleted too. This might be an isolated case. Rowdy -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
