{"push_id":785072261,"size":1,"distinct_size":1,"ref":"refs/heads/69-serial-nu","head":"a772a239cdd88a1709a8c192bde00130aa04f7c2","before":"d6527141eef7dc9296e68469c671188bc795b012","commits":[{"sha":"a772a239cdd88a1709a8c192bde00130aa04f7c2","author":{"email":"cb7881f9c19c34ab943d89f9d96f70beb9a7c0e5@gmail.com","name":"cecilia-donnelly"},"message":"Save serial number in \"Requests\" table: #69\n\nCreate a serial number based on date and number of requests submitted\nthat date.  Save it to a new \"serial\" column in the \"Requests\" table.\n\nNote that there is a possibility at the moment that we could have a\nduplicate serial number, because it is constructed from the date and the\ncount of requests submitted on that date.  If two requests are being\nsaved at the same time, then they might get the same count of\nalready-saved requests and then would have the same serial number.\n\nAs written in this commit, the serial number is added in an \"update.\"\nIn the next commit, I might construct and include it in the initial\nrequest to be saved.\n\nI added the serial column to the \"Requests\" table in this commit, but it\nmight be better to add it in a migration or via manual SQL.","distinct":true,"url":"https://api.github.com/repos/redcross/smoke-alarm-portal/commits/a772a239cdd88a1709a8c192bde00130aa04f7c2"}]}