1. 03 Oct, 2017 1 commit
  2. 01 Aug, 2017 3 commits
  3. 04 Jul, 2017 1 commit
  4. 04 Jun, 2017 2 commits
  5. 24 May, 2017 1 commit
  6. 23 May, 2017 1 commit
  7. 01 May, 2017 1 commit
  8. 15 Apr, 2017 1 commit
  9. 14 Apr, 2017 1 commit
  10. 13 Apr, 2017 3 commits
  11. 23 Jan, 2017 2 commits
  12. 21 Jan, 2017 1 commit
    • Pedro M. Baeza's avatar
      [ADD] convert_binary_field_to_attachment · d7fa29b6
      Pedro M. Baeza authored
      This method converts the 8.0 binary fields to attachments like Odoo 9.0
      makes with the new attachment=True attribute. It has to be called on
      post-migration script, as there's a call to get the res_name of the
      target model, which is not yet loaded on pre-migration.
      
      You need to rename the involved column in pre-migration script if you
      don't want to lose your data in the process.
      
      This method also removes after the conversion the source column for
      avoiding data duplication.
      
      This is done through Odoo ORM, because there's a lot of logic associated
      with guessing MIME type, format and length, file saving in store...
      that is doesn't worth to recreate it via SQL as there's not too much
      performance problem.
      
      :param env: Odoo environment
      :param field_spec: A dictionary with the ORM model name as key, and as
          dictionary values a tuple with:
              * field name to be converted as attachment as first element.
              * SQL column name that contains actual data as second element. If
                the second element is None, then the column name is taken
                calling `get_legacy_name` method, which is the typical technique.
      
      * field name to be converted as attachment as first element.
      * SQL column name that contains actual data as second element. If
        the second element is None, then the column name is taken
        calling `get_legacy_name` method.
      d7fa29b6
  13. 10 Jan, 2017 1 commit
    • Pedro M. Baeza's avatar
      [FIX] update_module_names: Rename non updated XML-ID occurences · c049180a
      Pedro M. Baeza authored
      Leaving untouched the non update ir.model.data entries, there are
      problems loading the database when the migration ends, as some
      of the related records can be assets, views...
      
      Renaming the entries to an unique name (generated from ID), we
      assure Odoo's update process removed them when updating the target
      module. If we would remove it them instead, we will need to remove
      manually the related resources as well, so this is the best
      strategy.
      c049180a
  14. 29 Dec, 2016 1 commit
  15. 27 Dec, 2016 5 commits
  16. 02 Dec, 2016 1 commit
  17. 07 Nov, 2016 1 commit
  18. 17 Oct, 2016 2 commits
  19. 11 Oct, 2016 1 commit
  20. 10 Oct, 2016 1 commit
  21. 09 Oct, 2016 1 commit
  22. 08 Oct, 2016 1 commit
  23. 07 Oct, 2016 3 commits
  24. 26 Aug, 2016 2 commits
  25. 29 Jul, 2016 1 commit
    • David Arnold's avatar
      [IMP] clarifying docstring · a9e81757
      David Arnold authored
      - Clarify that some fields are not supported.
      (it is implicit in columns != fields, but explicitly is more friendly)
      a9e81757
  26. 28 Jul, 2016 1 commit