{"comment":{"created_at":"2011-10-14T13:44:32Z","body":"Any word on this?","updated_at":"2011-10-14T13:44:32Z","url":"https://api.github.com/repos/EllisLab/CodeIgniter/issues/comments/2406666","id":2406666,"user":{"avatar_url":"https://secure.gravatar.com/avatar/185f81bb31e0f2f6551bafc5279ce344?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"185f81bb31e0f2f6551bafc5279ce344","url":"https://api.github.com/users/kutothe","id":334225,"login":"kutothe"}},"action":"created","issue":{"number":276,"created_at":"2011-08-23T04:12:17Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"As of 2.0.3, visibility is set to *protected* on the active record reset functions (_reset_select(), _reset_write()). I realize this conforms cleanly with the previously-unenforced private status of these functions -- but do we actually need/want *protected* visibility now that we're enforcing visibility in PHP5? \r\n\r\nSeems to me that there should be a way to uniformly clear query-related active record bits from controllers/models/libraries and opening up these functions is an easy way to do that.\r\n\r\nReference: **system/database/DB_active_rec.php** - Lines 1995 and 2027","comments":49,"title":"Visibility of reset functions in Active Record class","updated_at":"2011-10-14T13:44:32Z","url":"https://api.github.com/repos/EllisLab/CodeIgniter/issues/276","id":1463414,"assignee":null,"milestone":null,"closed_at":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/8d7315859f4c823cc6858bcfd6540412?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"8d7315859f4c823cc6858bcfd6540412","url":"https://api.github.com/users/cs-rhett","id":894513,"login":"cs-rhett"},"html_url":"https://github.com/EllisLab/CodeIgniter/issues/276","labels":[],"state":"open"},"legacy":{"issue_id":1463414,"comment_id":2406666}}