Changes between Version 3 and Version 4 of Ticket #1077


Ignore:
Timestamp:
05/08/11 18:58:07 (3 years ago)
Author:
kindly
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1077 – Description

    v3 v4  
    1111 
    1212 * Difficult to query revision history. Currently we have a way of finding out the diffs of particular packages.  These diffs *include* changes to objects associated with packages (i.e a resource attached to a package).  With the new model the only way to get this information is by looking in the json stored in the change object which is very awkward. 
    13   * RP: not sure this is true. You can query on object id very easily in the changeset model. Possible complication here is working out what objects are associated to say a package (e.g. have to look up ids of package_tags) but this does not seem more problematic than what you would do in other model to achieve the same ends. 
     13  * RP: not sure this is true. You can query on object id very easily in the changeset model. Possible complication here is working out what objects are associated to say a package (e.g. have to look up ids of package_tags) but this does not seem more problematic than what you would do in other model to achieve the same ends.s  
     14    * DR: In looking for related objects we do joins between revision tables and the main tables.  For example we join the package_extras_revision table to the package table.  We could not do this with the new model as we would need to look into change object table dict for the join, which is painful.  Also the object_ids are tuples as the moment which is difficult to join on. 
    1415 
    1516 * Does not give us anything extra if we simplify our use of vdm currently. (see alternative below) 
    1617  * RP: not quite true. E.g. pending support and API. 
     18   * DR: pending support would be there if we did not use any stateful lists/dicts and use vdm as a copy on write only with revision_id only.  I do not know what you mean by api. 
    1719 
    1820 * A large change to database structure needs to happen.