)]}'
{
  "commit": "f48ef702daf80f13b896eb6da4f81b0345ec2edf",
  "tree": "75a1e04723656f3ecc1753839aa6a7172b034410",
  "parents": [
    "d91e224391f557466bfaa091ca761056ccecf320"
  ],
  "author": {
    "name": "Nick Vatamaniuc",
    "email": "vatamane@apache.org",
    "time": "Wed Apr 22 12:25:31 2020 -0400"
  },
  "committer": {
    "name": "Nick Vatamaniuc",
    "email": "vatamane@apache.org",
    "time": "Wed Apr 22 12:39:41 2020 -0400"
  },
  "message": "Do not commit read-only transactions\n\nThis might save a round-trip to the network thread [1]. It also follows the\nrecommendation in the C api docs [2].\n\n[1] https://forums.foundationdb.org/t/performance-of-read-only-transactions/1998\n[2] https://apple.github.io/foundationdb/api-c.html#c.fdb_transaction_commit\n\nHowever, it turns out in order for the watches to fire the read-only\ntransaction still has to commit, so avoid this optimization if has_watches(Tx)\nis true.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2b62b910f4525beebec5795b531b25ad8684b739",
      "old_mode": 33188,
      "old_path": "src/erlfdb.erl",
      "new_id": "b50f8437a550b29129dd28a634b6cf475f780fc9",
      "new_mode": 33188,
      "new_path": "src/erlfdb.erl"
    }
  ]
}