From cb29bcb923804e844411fb4872f55993bf29ee91 Mon Sep 17 00:00:00 2001 From: rowanbeentje Date: Tue, 8 May 2012 01:03:31 +0000 Subject: Rework connection loss handling in SPMySQL, particularly to improve background loss of connections: - Attempt to fix a condition causing a reconnection loop by fixing the order of connection state check and a query variable - If a connection is lost in the background, only attempt a single reconnect instead of requiring user intervention at once - Add a new connection state to handle background disconnects - If the connection has been lost in the background but is about to be used, reconnect it automatically (informing the user of loss if appropriate) - Don't attempt background reconnections if the connection has not been used for some time (Also update localisable strings, and tweak navigator controller connection usage) --- .../Source/SPMySQLConnection Categories/Querying & Preparation.m | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Frameworks/SPMySQLFramework/Source/SPMySQLConnection Categories/Querying & Preparation.m') diff --git a/Frameworks/SPMySQLFramework/Source/SPMySQLConnection Categories/Querying & Preparation.m b/Frameworks/SPMySQLFramework/Source/SPMySQLConnection Categories/Querying & Preparation.m index 46615cae..0af0684a 100644 --- a/Frameworks/SPMySQLFramework/Source/SPMySQLConnection Categories/Querying & Preparation.m +++ b/Frameworks/SPMySQLFramework/Source/SPMySQLConnection Categories/Querying & Preparation.m @@ -235,7 +235,7 @@ // Ensure per-thread variables are set up [self _validateThreadSetup]; - // Check the connection if necessary, returning nil if the query couldn't be validated + // Check the connection if necessary, returning nil if the state couldn't be validated if (![self _checkConnectionIfNecessary]) return nil; // Determine whether a maximum query size needs to be restored from a previous query -- cgit v1.2.3