From 80ad102bdb58a967358c8d4a2294879884a4c16f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sa=C5=A1a=20=C5=BDivkov?= Date: Tue, 4 Nov 2014 14:30:02 +0100 Subject: [PATCH] Bump gwtorm to 1.14 - solves the primary key column order bug As described in [1], due to a gwtorm bug the primary key column order for compound keys was wrong for some Gerrit database tables. This causes poor performance for those SQL queries which rely on using a prefix of the primary key column sequence in their WHERE conditions. NOTE: this change solves the problem for new Gerrit sites. For existing Gerrit sites, created using Gerrit 2.6 or newer we will need a migration (in the master branch) and a site program (in older releases) in order to fix the primary keys. [1] https://gerrit-review.googlesource.com/61092 Change-Id: Ibfaeeb4b54468608b28c3352fe128ee148e3c0b9 --- lib/BUCK | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/lib/BUCK b/lib/BUCK index 687060994d..18e27b89ae 100644 --- a/lib/BUCK +++ b/lib/BUCK @@ -25,12 +25,11 @@ define_license(name = 'DO_NOT_DISTRIBUTE') maven_jar( name = 'gwtorm', - id = 'com.google.gerrit:gwtorm:1.13', - bin_sha1 = 'f522e05ca280335f8f8ba63c9c3e1b36be6ca7c2', - src_sha1 = '81bd99d55be872cd2fc52611f92cf5f3a64ffe8b', + id = 'com.google.gerrit:gwtorm:1.14', + bin_sha1 = '7e7562d2a8ae233ac9f23ec90dee1a01646483c0', + src_sha1 = 'ae991fdefe5e92ee7ed754786b924dc1ec119a8b', license = 'Apache2.0', deps = [':protobuf'], - repository = GERRIT, ) maven_jar(