aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorrowanbeentje <rowan@beent.je>2014-06-23 02:08:14 +0100
committerrowanbeentje <rowan@beent.je>2014-06-23 02:08:14 +0100
commit0c2ea8b95e4f85470af1e917e0d4560e42f35c3e (patch)
tree86178875dd4b8e36d23ef78d92f4ece750eb01bf
parent185a29c013fdf8b43ef7dc5e95da4c1aa8df34e0 (diff)
downloadsequelpro-0c2ea8b95e4f85470af1e917e0d4560e42f35c3e.tar.gz
sequelpro-0c2ea8b95e4f85470af1e917e0d4560e42f35c3e.tar.bz2
sequelpro-0c2ea8b95e4f85470af1e917e0d4560e42f35c3e.zip
Don't force relation clear on table update, as it now uses notifications to update itself; this will improve table switching speed significantly on laggy connections due to a forced information re-fetch
-rw-r--r--Source/SPDatabaseViewController.m3
1 files changed, 2 insertions, 1 deletions
diff --git a/Source/SPDatabaseViewController.m b/Source/SPDatabaseViewController.m
index 15b08907..c1823661 100644
--- a/Source/SPDatabaseViewController.m
+++ b/Source/SPDatabaseViewController.m
@@ -564,11 +564,12 @@
// Clear any views which haven't been loaded as they weren't visible. Note
// that this should be done after reloading visible views, instead of clearing all
// views, to reduce UI operations and avoid resetting state unnecessarily.
+ // Some views (eg TableRelations) make use of the SPTableChangedNotification and
+ // so don't require manual clearing.
if (!structureLoaded) [tableSourceInstance loadTable:nil];
if (!contentLoaded) [tableContentInstance loadTable:nil];
if (!statusLoaded) [[extendedTableInfoInstance onMainThread] loadTable:nil];
if (!triggersLoaded) [[tableTriggersInstance onMainThread] resetInterface];
- if (!relationsLoaded) [[tableRelationsInstance onMainThread] refreshRelations:self];
// If the table row counts an inaccurate and require updating, trigger an update - no
// action will be performed if not necessary