Use a non-volatile variable to avoid warning

Testing the value of a volatile entity for nullness doesn't give any
clue on its *continued* nullness. The tooling knows that and complains.

1 files changed, 3 insertions, 2 deletions

diff --git a/main/src/cgeo/geocaching/DataStore.java b/main/src/cgeo/geocaching/DataStore.java
index 0f9f6bf..d36a9c9 100644
--- a/main/src/cgeo/geocaching/DataStore.java
+++ b/main/src/cgeo/geocaching/DataStore.java
@@ -3001,8 +3001,9 @@ public class DataStore {
 
         private static void clearPreparedStatements() {
             for (final PreparedStatement preparedStatement : statements) {
-                if (preparedStatement.statement != null) {
-                    preparedStatement.statement.close();
+                final SQLiteStatement statement = preparedStatement.statement;
+                if (statement != null) {
+                    statement.close();
                     preparedStatement.statement = null;
                 }
             }