[Groonga-commit] groonga/groonga-admin at 4d4d0af [master] Use "schema" response instead of "table_list" response to build schema object

Back to archive index

YUKI Hiroshi null+****@clear*****
Wed Sep 21 16:18:09 JST 2016


YUKI Hiroshi	2016-09-21 16:18:09 +0900 (Wed, 21 Sep 2016)

  New Revision: 4d4d0aff2c0d885f99e316f0a5f5a835251d8fef
  https://github.com/groonga/groonga-admin/commit/4d4d0aff2c0d885f99e316f0a5f5a835251d8fef

  Merged eebf840: Merge pull request #10 from groonga/features/migrate-table_list-to-schema

  Message:
    Use "schema" response instead of "table_list" response to build schema object

  Modified files:
    app/scripts/services/schema-loader.js

  Modified: app/scripts/services/schema-loader.js (+2 -4)
===================================================================
--- app/scripts/services/schema-loader.js    2016-09-21 16:17:26 +0900 (c54efa7)
+++ app/scripts/services/schema-loader.js    2016-09-21 16:18:09 +0900 (ff873e7)
@@ -181,11 +181,9 @@ angular.module('groongaAdminApp')
 
       function fetchTables(schema) {
         schema.tables = {};
-        return client.execute('table_list')
+        return client.execute('schema')
           .success(function(response) {
-            response.tables().forEach(function(table) {
-              schema.tables[table.name] = table;
-            });
+            schema.tables = response.tables();
             resolveTables(schema);
 
             var fetchColumnsTasks = [];
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-commit mailing list
Back to archive index