You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ambari.apache.org by mp...@apache.org on 2016/04/28 16:11:58 UTC
ambari git commit: AMBARI-16159. Syntax error in MySQL DDL script.
(mpapirkovskyy)
Repository: ambari
Updated Branches:
refs/heads/trunk 32e437d42 -> 0fa71ff92
AMBARI-16159. Syntax error in MySQL DDL script. (mpapirkovskyy)
Project: http://git-wip-us.apache.org/repos/asf/ambari/repo
Commit: http://git-wip-us.apache.org/repos/asf/ambari/commit/0fa71ff9
Tree: http://git-wip-us.apache.org/repos/asf/ambari/tree/0fa71ff9
Diff: http://git-wip-us.apache.org/repos/asf/ambari/diff/0fa71ff9
Branch: refs/heads/trunk
Commit: 0fa71ff92f25cc03289b41ef9599bdd79f6052e8
Parents: 32e437d
Author: Myroslav Papirkovskyi <mp...@hortonworks.com>
Authored: Thu Apr 28 17:09:10 2016 +0300
Committer: Myroslav Papirkovskyi <mp...@hortonworks.com>
Committed: Thu Apr 28 17:09:10 2016 +0300
----------------------------------------------------------------------
ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/ambari/blob/0fa71ff9/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
----------------------------------------------------------------------
diff --git a/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql b/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
index bdbf461..9a20b8c 100644
--- a/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
+++ b/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
@@ -843,7 +843,7 @@ CREATE INDEX idx_hrc_request_id ON host_role_command (request_id);
CREATE INDEX idx_hrc_status_role ON host_role_command (status, role);
CREATE INDEX idx_rsc_request_id ON role_success_criteria (request_id);
--------- altering tables by creating foreign keys ----------
+-- ------ altering tables by creating foreign keys ----------
-- #1: This should always be an exceptional case. FK constraints should be inlined in table definitions when possible
-- (reorder table definitions if necessary).
-- #2: Oracle has a limitation of 30 chars in the constraint names name, and we should use the same constraint names in all DB types.