{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":19038193,"defaultBranch":"main","name":"slaq","ownerLogin":"godenji","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2014-04-22T17:06:56.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/238557?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1716690554.0","currentOid":""},"activityList":{"items":[{"before":"2eede53ee76ff6d1a540a06e3f999970e89a5f17","after":"a5d1d5c25184ffb44aaf3ec26d3cee031c1ae89d","ref":"refs/heads/main","pushedAt":"2024-07-01T15:43:23.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"godenji","name":"N.S. Cutler","path":"/godenji","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/238557?s=80&v=4"},"commit":{"message":"implement lock-free query template update/delete options\n\nExisting update/delete options available via `mutate` perform a \"SELECT\n... FOR UPDATE\" row level lock prior to executing target action. For\nhigh contention scenarios this can be desirable (i.e. to avoid\ntransaction thrashing), but in other cases performing a select, followed\nby an update/delete, followed by an additional select (by the JDBC driver to\nreturn affected rows) can be wasteful overhead.\n\nThe lock-free update/delete alternatives provided here\nallow for direct execution of UPDATE/DELETE prepared statements.","shortMessageHtmlLink":"implement lock-free query template update/delete options"}},{"before":"61f6326edfee2dff4bc8405abe04416d6c4c3467","after":"2eede53ee76ff6d1a540a06e3f999970e89a5f17","ref":"refs/heads/main","pushedAt":"2024-06-27T15:45:53.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"godenji","name":"N.S. Cutler","path":"/godenji","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/238557?s=80&v=4"},"commit":{"message":"prefix schema name (if exist) to table name in delete statements","shortMessageHtmlLink":"prefix schema name (if exist) to table name in delete statements"}},{"before":"a5ccd9c678b415aee7ff92724f4e68e698b869d3","after":"61f6326edfee2dff4bc8405abe04416d6c4c3467","ref":"refs/heads/main","pushedAt":"2024-06-20T00:44:57.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"godenji","name":"N.S. Cutler","path":"/godenji","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/238557?s=80&v=4"},"commit":{"message":"upgrade connector/J to latest (moved to new maven repo)","shortMessageHtmlLink":"upgrade connector/J to latest (moved to new maven repo)"}},{"before":null,"after":"37e81ba15deb58873e300cec443e6c11a2173394","ref":"refs/heads/master","pushedAt":"2024-05-26T02:29:14.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"godenji","name":"N.S. Cutler","path":"/godenji","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/238557?s=80&v=4"},"commit":{"message":"further gymnastics with subqueries\n\nThis should complete the work around subqueries yielding full tables.\nPrior commit (9fb3f83b353c89911f4bc0c5f266eb8bf1178390) did not properly\nhandle outer where/group by/order by clauses.\n\nThis commit adds a new `maybeNamed: Option[NamedColumn[_]]` to\n`SubqueryColumn`, which is used to match column operations (equality,\naggregation, etc.) to target subquery table/column -- e.g. \"where t1.c1 =\nt1.c2\" instead of erroneous \"where t2.id = t3.id\" (since table aliases\nt2 & t3 don't exist, all subquery columns are referenced under a single\nsubquery table alias tN).","shortMessageHtmlLink":"further gymnastics with subqueries"}},{"before":"37e81ba15deb58873e300cec443e6c11a2173394","after":null,"ref":"refs/heads/master","pushedAt":"2024-05-26T02:29:04.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"godenji","name":"N.S. Cutler","path":"/godenji","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/238557?s=80&v=4"}},{"before":null,"after":"a5ccd9c678b415aee7ff92724f4e68e698b869d3","ref":"refs/heads/main","pushedAt":"2024-05-26T02:25:27.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"godenji","name":"N.S. Cutler","path":"/godenji","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/238557?s=80&v=4"},"commit":{"message":"rewrite fixes for Scala 3.5 upgrade (much *faster* build times now)","shortMessageHtmlLink":"rewrite fixes for Scala 3.5 upgrade (much *faster* build times now)"}},{"before":"3e3a6bf3298faf7009d097c60df89982ed0a04a4","after":"37e81ba15deb58873e300cec443e6c11a2173394","ref":"refs/heads/master","pushedAt":"2023-03-22T23:50:36.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"godenji","name":"N.S. Cutler","path":"/godenji","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/238557?s=80&v=4"},"commit":{"message":"further gymnastics with subqueries\n\nThis should complete the work around subqueries yielding full tables.\nPrior commit (9fb3f83b353c89911f4bc0c5f266eb8bf1178390) did not properly\nhandle outer where/group by/order by clauses.\n\nThis commit adds a new `maybeNamed: Option[NamedColumn[_]]` to\n`SubqueryColumn`, which is used to match column operations (equality,\naggregation, etc.) to target subquery table/column -- e.g. \"where t1.c1 =\nt1.c2\" instead of erroneous \"where t2.id = t3.id\" (since table aliases\nt2 & t3 don't exist, all subquery columns are referenced under a single\nsubquery table alias tN).","shortMessageHtmlLink":"further gymnastics with subqueries"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNy0wMVQxNTo0MzoyMy4wMDAwMDBazwAAAARz79rK","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNy0wMVQxNTo0MzoyMy4wMDAwMDBazwAAAARz79rK","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wMy0yMlQyMzo1MDozNi4wMDAwMDBazwAAAAMJR4SL"}},"title":"Activity · godenji/slaq"}