{"push_id":883262871,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"c1db13f716233df768b4fb89decb5e603ae532e3","before":"9e9a15effb72d22725919e912a889290f07ae026","commits":[{"sha":"c1db13f716233df768b4fb89decb5e603ae532e3","author":{"email":"4d6ffa4b6f6d1802f72f875ea2cf94e8200ee8e4@ymb.net","name":"Trinity Quirk"},"message":"Updated login-related queries in MySQL module\n\nNow that we're actually accepting logins, and the server seems to\nbe running pretty well, we messed with the database structure and\nactions a bit.  The open_new_login and close_open_login methods\nwere unimplemented, so we finished them up.\n\nWe needed the server ID value in a couple of the login-related\nmethods, so we've added a member to keep track of it, and within\nthe MySQL object, we're retrieving it in the connect routine if\nit's not already set.\n\nThe default \"no access\" value for checking server authorization is\nnow 1, rather than 0, so that will be our default return value.\n\nAlso some small tweaks to the MySQL schema based on the results of\nsome testing.","distinct":true,"url":"https://api.github.com/repos/adminspotter/r9/commits/c1db13f716233df768b4fb89decb5e603ae532e3"}]}