{"push_id":1192135743,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"6894c8ecaac64f4b5baaa383ea689e658782d05e","before":"1605bf1cdb7c4f7bd10f3f215451195d3286fedf","commits":[{"sha":"f09bb42d67d879ef292a8dc9654f41308fd1a6d8","author":{"name":"koljonen","email":"0fc30a9ef2eda191a27d014f5b14fd4e2ad190eb@outlook.com"},"message":"Better scoping for tables in insert statements\n\nThis commit makes it so that given `INSERT INTO foo(<cursor1>) SELECT <cursor2> FROM bar;`, we suggest `bar` columns for `<cursor2>` and `foo` columns for `<cursor1>`. Previous behaviour is sugggesting columns from both tables in both cases.","distinct":false,"url":"https://api.github.com/repos/koljonen/pgcli/commits/f09bb42d67d879ef292a8dc9654f41308fd1a6d8"},{"sha":"6894c8ecaac64f4b5baaa383ea689e658782d05e","author":{"name":"Amjith Ramanujam","email":"5b0f3928496d6ad534c145ed68c9ef749ed0e784@gmail.com"},"message":"Merge pull request #543 from dbcli/koljonen/insert_table_scope\n\nBetter scoping for tables in insert statements","distinct":true,"url":"https://api.github.com/repos/koljonen/pgcli/commits/6894c8ecaac64f4b5baaa383ea689e658782d05e"}]}
{"actor":{"display_login":"koljonen"}}