From 17645c11a21e8bbb92adf3dbd1a3e69c3ab44ce8 Mon Sep 17 00:00:00 2001
From: Robert von Burg <eitch@eitchnet.ch>
Date: Thu, 18 Jun 2020 16:26:51 +0200
Subject: [PATCH] [Fix] Gracefully handle not being able to update a LogMessage

---
 .../persistence/postgresql/PostgreSqlLogMessageDao.java   | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/li.strolch.persistence.postgresql/src/main/java/li/strolch/persistence/postgresql/PostgreSqlLogMessageDao.java b/li.strolch.persistence.postgresql/src/main/java/li/strolch/persistence/postgresql/PostgreSqlLogMessageDao.java
index c9216b41d..8a82981e0 100644
--- a/li.strolch.persistence.postgresql/src/main/java/li/strolch/persistence/postgresql/PostgreSqlLogMessageDao.java
+++ b/li.strolch.persistence.postgresql/src/main/java/li/strolch/persistence/postgresql/PostgreSqlLogMessageDao.java
@@ -121,12 +121,8 @@ public class PostgreSqlLogMessageDao implements LogMessageDao {
 			ps.setString(1, logMessage.getState().name());
 			ps.setString(2, logMessage.getId());
 
-			int count = ps.executeUpdate();
-			if (count != 1) {
-				throw new StrolchPersistenceException(MessageFormat
-						.format("Expected to update 1 log_message record, but updated {0} for LogMessage {1}", count,
-								logMessage.getId())); //$NON-NLS-1$
-			}
+			// we ignore the number of updates, as the message might have been deleted meanwhile
+			ps.executeUpdate();
 
 		} catch (SQLException e) {
 			throw new StrolchPersistenceException(MessageFormat