Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
erp5 erp5
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 0
    • Merge requests 0
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • Romain Courteaud
  • erp5erp5
  • Repository

Switch branch/tag
  • erp5
  • bt5
  • erp5_upgrader
  • TestTemplateItem
  • portal_components
  • test.erp5.testUpgrader.py
Find file BlameHistoryPermalink
  • Jérome Perrin's avatar
    upgrader: really execute the whole `upgrade` step in one transaction · 62a9d4c8
    Jérome Perrin authored Jul 26, 2016
    Documentation says this step is done in one transaction, so implement
    this as documented.
    
    Detecting developer mistake and automagically running this step in smaller
    transactions if more than 100 documents seems unnecessary. At least, it
    contredicts documentation.
    62a9d4c8
test.erp5.testUpgrader.py 30.7 KB
EditWeb IDE

Replace test.erp5.testUpgrader.py

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7