{"issue":{"pull_request":{"diff_url":"https://github.com/EllisLab/CodeIgniter/pull/632.diff","html_url":"https://github.com/EllisLab/CodeIgniter/pull/632","patch_url":"https://github.com/EllisLab/CodeIgniter/pull/632.patch"},"state":"open","user":{"avatar_url":"https://secure.gravatar.com/avatar/ea8d71663c1c8e5dc2a0fb5d2f8c8ea8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"ea8d71663c1c8e5dc2a0fb5d2f8c8ea8","url":"https://api.github.com/users/jtboofle","login":"jtboofle","id":1157049},"milestone":null,"labels":[],"updated_at":"2011-10-28T05:20:32Z","assignee":null,"comments":2,"closed_at":null,"url":"https://api.github.com/repos/EllisLab/CodeIgniter/issues/632","body":"For those of us with 'special' database needs (in my case, connecting to DB2 and using non-standard field names in the session table), having all the database calls embedded in the session class is a pain in the keister.  I've moved them out into a sessions model which makes fiddling around with session handling a simple matter of overriding 5 function calls. ","html_url":"https://github.com/EllisLab/CodeIgniter/issues/632","title":"Moving database calls out of Session library into sessions model","number":632,"id":2075516,"created_at":"2011-10-28T04:08:36Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/ea8d71663c1c8e5dc2a0fb5d2f8c8ea8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"ea8d71663c1c8e5dc2a0fb5d2f8c8ea8","url":"https://api.github.com/users/jtboofle","login":"jtboofle","id":1157049},"updated_at":"2011-10-28T05:20:32Z","url":"https://api.github.com/repos/EllisLab/CodeIgniter/issues/comments/2552662","body":"Support for DB2 would be great, though my situation is probably pretty unusual -- I doubt too many people are running CI on an IBM iSeries.  I actually ended up making native database calls (it looks a lot like PDO, but even more of a pain) and not using the ActiveRecord tools at all.  I might try to wrap my code in something that's more general-purpose, but right now it's not fit for public consumption.\r\n\r\nMoving the database code out helps everyone who has funky database issues.  I wrote (and re-wrote) my data access libraries repeatedly trying to get something that would work well on the iSeries but once I had the database calls moved out of the session class, I didn't have to muck around in there again.  I just overrode the model.","id":2552662,"created_at":"2011-10-28T05:20:32Z"}}