{"issue":{"created_at":"2011-11-19T00:30:39Z","state":"closed","updated_at":"2011-11-25T17:12:51Z","user":{"gravatar_id":"fe6f815450bca970d45b9674eb137b11","id":129741,"url":"https://api.github.com/users/dacc","login":"dacc","avatar_url":"https://secure.gravatar.com/avatar/fe6f815450bca970d45b9674eb137b11?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":6,"body":"Our (legacy) database has enum columns with values \"true\" and \"false\" -- silly I know.  jOOQ dutifully reads them, but of course we end up with the reserved words \"true\" and \"false\" as attempted enum field names, breaking the compiler.","assignee":null,"id":2286213,"number":4,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[],"title":"Enums With \"true\" and \"false\" Values Left Literally Interpreted","closed_at":"2011-11-25T17:12:51Z","html_url":"https://github.com/lukaseder/jOOQ/issues/4","url":"https://api.github.com/repos/lukaseder/jOOQ/issues/4","milestone":null},"action":"closed"}