{"push_id":1311224516,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"be5f19260f5024779b4a40340a566cf251d1daea","before":"5c75efa812bfdd6aa530c1bfbcfbc21eb7835658","commits":[{"sha":"d2650c688b22f2912225fb107405b11e1731826e","author":{"name":"Sam Stenvall","email":"332e8de8f3445d3ebf75bf2f4cfcc79d152e1b23@nordsoftware.com"},"message":"[pvr] fix potential SQL constraint integrity violation\n\nSupersedes #8963\nFixes trac #16031\nCloses https://github.com/kodi-pvr/pvr.hts/issues/172\n\nThis fixes the problem without bumping the database version so it should be more possibly to get it merged for V17.\n\nBasically the code that persists channels has been made smarter. Instead of just blindly looking at the primary key stored in the object we query the database to check if a channel with the unique ID and client ID already exists. If it does, we update that channel, if not we create a new channel. There is more background information in the referenced PRs.\n\nThis fix also has the added side-effect that it increases database performance. While a new SELECT statement has been added, we now do an UPDATE instead of a REPLACE INTO which prevents indexes from having to be re-calculated (REPLACE INTO basically does a DELETE followed by an INSERT). This also means we don't need to worry about the channel ID changing after the channel has been updated (which was a side effect of using REPLACE INTO).","distinct":true,"url":"https://api.github.com/repos/starlightknight/xbmc/commits/d2650c688b22f2912225fb107405b11e1731826e"},{"sha":"be5f19260f5024779b4a40340a566cf251d1daea","author":{"name":"Kai Sommerfeld","email":"6ed7d1c7f2caff6eac95fca9ba0a24b87973b23d@gmx.com"},"message":"Merge pull request #10507 from Jalle19/fix-pvr-database-access\n\nFix potential SQL constraint integrity violation in the PVR database","distinct":true,"url":"https://api.github.com/repos/starlightknight/xbmc/commits/be5f19260f5024779b4a40340a566cf251d1daea"}]}
{"actor":{"display_login":"starlightknight"}}