{"push_id":1259086286,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d88dc74f322b8707c7e3d2511575eec0d6db1443","before":"220772a6a96429a397f77587fafe7050fbcefa47","commits":[{"sha":"d88dc74f322b8707c7e3d2511575eec0d6db1443","author":{"name":"Torsten Bronger","email":"a0fbb8d01f2d7626cee64ee4e62f2a1197194f86@physik.rwth-aachen.de"},"message":"Revert \"Removed \"parent_topic\" from unique constraint for Topics.\"\n\nThis reverts commit 51be693af39f603bef1f65ee49b7f174ecf6e1cf.  Because the view\nallows duplicate topic names if the parent topic is different, and because this\nis conceptually a good thing, the DB constraints must allow this, too.\n\nSince the DB still cannot find duplicates if the parent topic is empty (see\nhttp://stackoverflow.com/a/33308014/188108 for details), I enforce it in the\n\"save\" method.","distinct":true,"url":"https://api.github.com/repos/juliabase/juliabase/commits/d88dc74f322b8707c7e3d2511575eec0d6db1443"}]}
{"actor":{"display_login":"bronger"}}