{"push_id":2882516203,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"329af7071ced73bef361b8569d329ef788755c2a","before":"d82693866de451d5e1af8ea2f215b05576bb7f3b","commits":[{"sha":"329af7071ced73bef361b8569d329ef788755c2a","author":{"name":"Will Smart","email":"9eb7e44de729649511a4bdc5dfc7297efc6da121@gmail.com"},"message":"- fixes the triggers in a few ways:\n  - now send out notifications _after_ the del/ins/upd\n  - shorter delays\n  - move the logic to send out notification into the model triggers (rather than the model_change_log triggers). This means that if an op produces a few changes (like a delete operation which may change a few fields) then only one notification is sent out and the delay is not triggered unnecessarily.\n  - Many fixups to how the retriggering sys works. Triggers are now cleaned up and remade correctly.\n- fix to allow row deletion to work.\n  - Rows are deleted by setting thier special field ‘*’ to null. (This makes logical sense as * will typically be taken to mean ‘all the fields’, and row deletion in NoBo is equiv in effect to setting all of the row’s fields to null, since fields in missing rows read as null.\n  - I prefer this kind of approach model[‘*’]=undefined to adding a special delete_row(id) function, at the base level at least. I may make a helper method to cover over the messy syntax.","distinct":true,"url":"https://api.github.com/repos/willsmart/nobo/commits/329af7071ced73bef361b8569d329ef788755c2a"}]}
{"actor":{"display_login":"willsmart"}}