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 141
    • Merge requests 141
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • erp5erp5
  • Merge requests
  • !9

Closed
Created Aug 02, 2015 by Kirill Smelkov@kirrOwner
  • Report abuse
Report abuse

[RFC] ERP5Type.Base: .serialize() is possible without writing object to DB

  • Overview 2
  • Commits 1
  • Changes 1000+

Hello,

I've noticed some project explicitly disable .serialize(), e.g. via passing serialize=False to BigFile._read_data() to avoid wasting disk space via not committing unchanged BTreeNode.

This can be avoided since ZODB provides explicit API to make sure object stays unchanged during commit, without marking it as changed - Connection.readCurrent(obj).

Thus this way if we fix .serialize() not to "change" object, we can drop workarounds to disable it everywhere. Also less space will be wasted in all places where .serialize() is used.

Not tested.

/cc @vpelletier, @jm, @seb

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: q/serialize-no-write
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7