From 201ce71fe6d155a067074f4687e03fbfe858bc63 Mon Sep 17 00:00:00 2001 From: Gokul Prathin Date: Tue, 27 Aug 2024 15:43:43 -0400 Subject: [PATCH] fix typo --- content/english/blog/h2_database_cleanup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/english/blog/h2_database_cleanup.md b/content/english/blog/h2_database_cleanup.md index a5fa149..396581f 100644 --- a/content/english/blog/h2_database_cleanup.md +++ b/content/english/blog/h2_database_cleanup.md @@ -14,7 +14,7 @@ While building our Geoweaver application with the H2 database, we came across an

-### Understanding H2’s Deletion Mechanism** +### Understanding H2’s Deletion Mechanism When you delete rows in most databases, you might expect those rows to be immediately removed from the database file. However, H2 operates differently. Instead of instantly deleting rows, H2 simply marks them as “deleted” within its system but doesn’t actually remove them from the file. This approach means that the space these rows occupy isn’t freed up immediately, which leads to the database file continuing to grow, even as the data you’ve deleted no longer serves any purpose.