Skip to content
Snippets Groups Projects
  1. Jul 10, 2013
    • Launchpad's avatar
      Launchpad automatic translations update. · 08b8d203
      Launchpad authored
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130709054516-gtc3o5y2e2ywv2ze
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130710055211-byl6v65puydy7lj8
      08b8d203
  2. Jul 08, 2013
  3. Jul 07, 2013
    • Launchpad's avatar
      Launchpad automatic translations update. · c0119a87
      Launchpad authored
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130706061750-b7mm65zaln6pacmc
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130707055412-bb9fnxig7ss4pugc
      c0119a87
  4. Jul 05, 2013
  5. Jul 04, 2013
  6. Jul 03, 2013
    • Olivier Dony's avatar
      [FIX] ir.ui.view: properly validate newly created inheriting views · eae2321c
      Olivier Dony authored
        
        When a new inheriting view is imported during a module
        installation, it is validated thanks to the _constraints
        on the ir.ui.view model. However the validation uses
        a rather convoluted system for validating the whole
        view tree at once (root view + all inherited changes)
        while only taking into account the views that belong
        to modules that are currently loaded.
        
        This complicated system is necessary to be able to
        operate on-the-fly at any point during the registry
        loading/initialization.
        
        Now because _constraints are checked during create()
        this particular validation happens *before* the
        external ID (ir.model.data entry) of that new view
        can be created (it obviously needs to wait until
        the view record is inserted). As a consequence the
        view validation cannot determine the module to
        which that new view belongs, and was erroneously
        ignoring it.
        Changing the view filtering to also include views
        from unknown modules fixes this transient problem,
        and also means that manually created inherited
        views will be validated during module init too.
      
      bzr revid: odo@openerp.com-20130703215704-x732bepiifvf4g3n
      eae2321c
  7. Jul 05, 2013
  8. Jul 03, 2013
  9. Jul 02, 2013
  10. Jul 01, 2013
    • Olivier Dony's avatar
      [FIX] procurement: background procurement scheduler should be working in batch... · 9b6f5dca
      Olivier Dony authored
      [FIX] procurement: background procurement scheduler should be working in batch mode, with one transaction per order
      
      A programming error during an older refactoring lead to
      the scheduler working with a single monolithic transaction.
      This could cause unnecessary resource contention, plus
      undesired rollback of all previous operations in the event
      of an exception during scheduling.
      
      bzr revid: odo@openerp.com-20130701163532-8bekn7sbb99ua08c
      9b6f5dca
  11. Jul 02, 2013
  12. Jun 28, 2013
  13. Jun 27, 2013
  14. Jun 26, 2013
  15. Jun 24, 2013
Loading