{"action":"created","issue":{"url":"https://api.github.com/repos/stefanofontanelli/ColanderAlchemy/issues/85","labels_url":"https://api.github.com/repos/stefanofontanelli/ColanderAlchemy/issues/85/labels{/name}","comments_url":"https://api.github.com/repos/stefanofontanelli/ColanderAlchemy/issues/85/comments","events_url":"https://api.github.com/repos/stefanofontanelli/ColanderAlchemy/issues/85/events","html_url":"https://github.com/stefanofontanelli/ColanderAlchemy/issues/85","id":73127947,"number":85,"title":"Handling JSON/JSONB columns","user":{"login":"miohtama","id":49922,"avatar_url":"https://avatars.githubusercontent.com/u/49922?v=3","gravatar_id":"","url":"https://api.github.com/users/miohtama","html_url":"https://github.com/miohtama","followers_url":"https://api.github.com/users/miohtama/followers","following_url":"https://api.github.com/users/miohtama/following{/other_user}","gists_url":"https://api.github.com/users/miohtama/gists{/gist_id}","starred_url":"https://api.github.com/users/miohtama/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/miohtama/subscriptions","organizations_url":"https://api.github.com/users/miohtama/orgs","repos_url":"https://api.github.com/users/miohtama/repos","events_url":"https://api.github.com/users/miohtama/events{/privacy}","received_events_url":"https://api.github.com/users/miohtama/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-05-04T21:07:15Z","updated_at":"2015-05-06T15:19:35Z","closed_at":null,"body":"Currently I am having some types in my models which are JSON/JSONB (PostgreSQL). The default `get_schema_from_column` cannot handle them. The optimal mapping for these columns, unless user-given override is in place, should be read only string.\r\n\r\nWould be be interested to cover this case in ColanderAlchemy core or should I keep it separate and maybe provide documentation how to handle the situation?"},"comment":{"url":"https://api.github.com/repos/stefanofontanelli/ColanderAlchemy/issues/comments/99510493","html_url":"https://github.com/stefanofontanelli/ColanderAlchemy/issues/85#issuecomment-99510493","issue_url":"https://api.github.com/repos/stefanofontanelli/ColanderAlchemy/issues/85","id":99510493,"user":{"login":"miohtama","id":49922,"avatar_url":"https://avatars.githubusercontent.com/u/49922?v=3","gravatar_id":"","url":"https://api.github.com/users/miohtama","html_url":"https://github.com/miohtama","followers_url":"https://api.github.com/users/miohtama/followers","following_url":"https://api.github.com/users/miohtama/following{/other_user}","gists_url":"https://api.github.com/users/miohtama/gists{/gist_id}","starred_url":"https://api.github.com/users/miohtama/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/miohtama/subscriptions","organizations_url":"https://api.github.com/users/miohtama/orgs","repos_url":"https://api.github.com/users/miohtama/repos","events_url":"https://api.github.com/users/miohtama/events{/privacy}","received_events_url":"https://api.github.com/users/miohtama/received_events","type":"User","site_admin":false},"created_at":"2015-05-06T15:19:35Z","updated_at":"2015-05-06T15:19:35Z","body":"The problem is this approach that you are putting form-related (UI) stuff in the models (data) (though just hints) - and at the end of this road is something horrible, as, for example, you start cross-import between UI and models.  Thus, I'd like to maintain separation between the form hints and the actual SQLAlchemy model.\r\n\r\nAlso the hint syntax in model is quite heavy, but this is more of a problem with Python itself.\r\n"}}