You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cayenne.apache.org by "Nikita Timofeev (Jira)" <ji...@apache.org> on 2020/11/05 13:33:00 UTC

[jira] [Closed] (CAY-2685) JsonType should use the actual JDBC type, not OTHER

     [ https://issues.apache.org/jira/browse/CAY-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nikita Timofeev closed CAY-2685.
--------------------------------
    Resolution: Fixed

https://github.com/apache/cayenne/commit/a7b36294d0559ef7c3dd4b75055fd96d99c05db4

> JsonType should use the actual JDBC type, not OTHER
> ---------------------------------------------------
>
>                 Key: CAY-2685
>                 URL: https://issues.apache.org/jira/browse/CAY-2685
>             Project: Cayenne
>          Issue Type: Bug
>    Affects Versions: 4.2.M2
>            Reporter: Andrus Adamchik
>            Assignee: Nikita Timofeev
>            Priority: Major
>             Fix For: 4.2.M3
>
>
> On some DBs there's no native JSON type. So we have to use a VARCHAR, but still map it to the new "org.apache.cayenne.value.Json". This causes exceptions (at least I saw it on Derby). To fix it, all the JsonType methods that hardcode Types.OTHER should pass the actual type to JDBC. It is available as a method parameter



--
This message was sent by Atlassian Jira
(v8.3.4#803005)