[
https://issues.apache.org/jira/browse/CAY-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796984#action_12796984
]
Evgeny Ryabitskiy commented on CAY-1354:
----------------------------------------
after some code inspection I found out that the problem is in JDBC drivers, we
are using metaData.getColumnClassName(position); that can return driver
specific JAVA type (how it was with Oracle).
My idea is to use Cayenne TypeMapping for it. So I changed few lines and wow...
we can delete all that Oracle stuff from my last commits :)))
It is funny.....
One thing is that we should document (I mean user documentation) this type
mapping.
> Wrong Types mapping for selected values in Row Queries
> ------------------------------------------------------
>
> Key: CAY-1354
> URL: https://issues.apache.org/jira/browse/CAY-1354
> Project: Cayenne
> Issue Type: Bug
> Components: Cayenne Core Library
> Affects Versions: 3.1M1
> Reporter: Evgeny Ryabitskiy
> Assignee: Evgeny Ryabitskiy
> Priority: Critical
> Fix For: 3.1M1
>
> Attachments: CAY-1354_TEST.patch, ReturnTypesMappingTest.java
>
>
> By default every SQL type is mapped to some Java type by modeler.
> I am expecting same behavior in common DataRow queries (without ORM).
> But in fact half of types are not mapped correctly....
> Attached JUnit test can to explain problem with more details...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
