Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Synopsis Synopsis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Extensions
  • SynopsisSynopsis
  • Issues
  • #7
Closed
Open
Issue created Oct 06, 2022 by Rich@artfulrobotReporter

Risk of missing data?

Hi.

I've just installed this and was looking at how it recalculates. I might have this wrong, but it seems that it truncates the main synopsis table, then does a big copy of data into it.

It made me think that if civiMail is busy doing a mailing which takes it over an hour and includes a token to a synopsis field, then there will be a time window during which the values don't exist for the contact civimail is processing.

I think it would safer to use a transaction for the empty-and-re-fill operation. That way the worst that happens is CiviMail gets a slightly out of date version.

The only problem I see with this is that we'd have to move away from TRUNCATE (because it exits a transaction), so we'd have to use DELETE FROM $synopsisTable instead which may be a bit slower.

Thoughts?

Assignee
Assign to
Time tracking