Possible "fix" for wrong cache key:
authorRoland Häder <roland@mxchange.org>
Thu, 25 Jul 2013 02:29:26 +0000 (02:29 +0000)
committerRoland Häder <roland@mxchange.org>
Thu, 25 Jul 2013 02:29:26 +0000 (02:29 +0000)
- $onlyKeys allows to set database table columns that shall be used for
  creating a cache key, this can be used to look for a node id/ip/port
  combination instead of the default session id.

application/hub/main/database/wrapper/node/class_NodeDistributedHashTableDatabaseWrapper.php

index 0beb31c0d3f02e1f81520bb205ab4824279a1b51..7870e0c22968837720d31da88c7e79df3ab9279e 100644 (file)
@@ -284,7 +284,16 @@ class NodeDistributedHashTableDatabaseWrapper extends BaseDatabaseWrapper implem
                $searchInstance->setLimit(1);
 
                // Query database and get a result instance back
-               $resultInstance = $this->doSelectByCriteria($searchInstance);
+               $resultInstance = $this->doSelectByCriteria(
+                       // Search instance
+                       $searchInstance,
+                       // Only look for these array elements ("keys")
+                       array(
+                               self::DB_COLUMN_NODE_ID,
+                               self::DB_COLUMN_EXTERNAL_IP,
+                               self::DB_COLUMN_LISTEN_PORT,
+                       )
+               );
 
                // Check if there is an entry
                $isRegistered = $resultInstance->valid();