I guess I'm too dumb, but if there's a transaction before and after which referential integrity of the DB if given, and the records of all tables involved are backed up on their respective updates, why are inactive records in the original tables needed? I understand that the backup records need to refer to the former IDs in the original tables, but why do the inactive records themselves need to exist?
Am Montag, 17. Februar 2014 22:08:17 UTC+1 schrieb Niphlod: > > the is_active = 0 is actually a good rationale because of relational > integrity. > Dropping a row with dependants record on it would mean dropping also the > dependant record(s), that can't be then "archived" properly. > > On Monday, February 17, 2014 2:02:36 PM UTC+1, Anthony wrote: >> >> On Monday, February 17, 2014 7:24:24 AM UTC-5, Horst Horst wrote: >>> >>> I don't understand the rationale behind the way record versioning is >>> implemented: If you delete a record, it is marked as is_active=False in the >>> original table, but it is also copied to the my_table_archive table. >>> >>> Why this doubling of data? And /if/ data is doubled, why then not >>> immediately when records are inserted (into both, the regular table and the >>> archive), so that deletion could indeed delete from the original table? >>> >> >> As mentioned >> here<http://web2py.com/books/default/chapter/29/09/access-control#Record-versioning>, >> >> deletion is only prevented if the table in question includes an "is_active" >> field. So, if you don't include an "is_active" field, you will get a >> complete record deletion after the archiving. >> >> You can also prevent the is_active behavior by using the >> Table._enable_record_versioning method rather than >> auth.enable_record_versioning. The former takes an "is_active" argument, >> which is used to specify the name of the "is_active" field (in case you >> want to name it something else) -- if you pass in any falsey value for that >> argument, you don't get the is_active behavior (even if the table does in >> fact include an "is_active" field). >> >> This could probably be clarified in the book (particularly since record >> versioning is discussed in two different places). >> >> Anthony >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
