--- title: Event Sourcing: undo set-remove-based bi-temporal events... description: Part thirteen of an event sourcing series tackles the problem of undoing events in a bi-temporal, set-remove-based model. The naive approach of overriding a... canonical: https://daily.dev/posts/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must-y6cpmwees twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Event Sourcing: undo set-remove-based bi-temporal events – because we must | daily.dev og:description: Part thirteen of an event sourcing series tackles the problem of undoing events in a bi-temporal, set-remove-based model. The naive approach of overriding a... og:url: https://daily.dev/posts/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must-y6cpmwees og:image: https://api.daily.dev/og/posts/y6cpMWeES.png og:image:alt: Event Sourcing: undo set-remove-based bi-temporal events – because we must og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Event Sourcing: undo set-remove-based bi-temporal events – because we must **[We Are .NET](https://daily.dev/sources/wearedotnet)** · 6 min read · 0 upvotes · 0 comments ## Summary Part thirteen of an event sourcing series tackles the problem of undoing events in a bi-temporal, set-remove-based model. The naive approach of overriding a wrong event with the same timestamp corrupts the timeline when subsequent events are added. Two solutions are compared: a simpler approach using 'undone' and 'undoneAt' columns to mark events as undone without losing historical meaning, and a more complex 'Undo event' approach that references events by effective and application timestamps. The author explains why the column-based approach is preferred for its simplicity and maintainability, and includes an F# code deep dive showing the implementation for a task-tracking feature. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Event Sourcing: set-and-remove-based bi-temporal events](https://daily.dev/posts/event-sourcing-set-and-remove-based-bi-temporal-events-8de56bzad) · We Are .NET · 1 upvotes · 0 comments - [Event Sourcing: the not-so-simple bi-temporal basics](https://daily.dev/posts/event-sourcing-the-not-so-simple-bi-temporal-basics-t4ntaclgn) · We Are .NET · 0 upvotes · 0 comments - [Event sourcing: non-bi-temporal events in a bi-temporal stream](https://daily.dev/posts/event-sourcing-non-bi-temporal-events-in-a-bi-temporal-stream-8scwvqj99) · We Are .NET · 0 upvotes · 0 comments --- Tags: [#architecture](https://daily.dev/tags/architecture), [#.net](https://daily.dev/tags/.net), [#domain-driven-design](https://daily.dev/tags/domain-driven-design), [#fsharp](https://daily.dev/tags/fsharp) [View this post on daily.dev](https://daily.dev/posts/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must-y6cpmwees) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Event Sourcing: undo set-remove-based bi-temporal events – because we must","url":"https://daily.dev/posts/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must-y6cpmwees","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must-y6cpmwees"},"datePublished":"2026-07-14T08:39:39.880Z","dateModified":"2026-07-14T09:57:56.920Z","description":"Part thirteen of an event sourcing series tackles the problem of undoing events in a bi-temporal, set-remove-based model. The naive approach of overriding a...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5177fe090a15411ee61d7666149ef693?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5177fe090a15411ee61d7666149ef693?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"We Are .NET","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"We Are .NET","logo":"https://media.daily.dev/image/upload/s--BsnVOa3i--/f_auto/v1718347410/logos/wearedotnet","url":"https://daily.dev/sources/wearedotnet"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must-y6cpmwees","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"architecture,.net,domain-driven-design,fsharp","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"We Are .NET","item":"https://daily.dev/sources/wearedotnet"},{"@type":"ListItem","position":3,"name":"Event Sourcing: undo set-remove-based bi-temporal events – because we must"}]} ```