<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Daniel Hartmann on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/daniel-hartmann/</link><description>Articles written by Daniel Hartmann on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 21 May 2026 10:09:00 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/daniel-hartmann/index.xml" rel="self" type="application/rss+xml"/><item><title>Implementing Soft Deletes in Java</title><link>https://foojayio.github.io/website/today/implementing-soft-deletes-in-java/</link><pubDate>Thu, 21 May 2026 10:09:00 +0000</pubDate><guid>https://foojayio.github.io/website/today/implementing-soft-deletes-in-java/</guid><description>&lt;h2 id="soft-deletes"&gt;What are soft deletes?&lt;/h2&gt;
&lt;p&gt;Usually, when deleting documents from a database, the entry is permanently gone and can not be recovered or accessed again.&lt;/p&gt;
&lt;p&gt;Sometimes data needs to be made unavailable for regular access without actually being removed from a database. A common example is a user deleting their account on a platform, but retention policies require you to keep all data related to that user for a certain period of time. At the same time, no data regarding that user is accessible on the platform. A soft delete is a treatment for a piece of data that ensures it is ignored by your application while actually still being stored in the database.&lt;/p&gt;</description></item></channel></rss>