[
https://issues.apache.org/jira/browse/CAY-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Ryabitskiy updated CAY-1354:
-----------------------------------
Attachment: CAY-1354_2.0.patch
This is patch for 2.0
To move logic of Java type resolving from driver to Cayenne type mapping.
Reason: Drivers can return here different types (even some specific like
com.oracle.TIMESTAMP)
3.1 trunk is already fixed.
Why 2.0 should be patched? Because current logic (witch returns driver specific
types) is really far from our last release ( 2.0.4 ) which doesn't rely on
drivers.
So I suggest to fix it in all branches (even 3.0 that is going to release soon).
> 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: Core Library
> Affects Versions: 3.1M1
> Reporter: Evgeny Ryabitskiy
> Assignee: Evgeny Ryabitskiy
> Priority: Critical
> Fix For: 3.1M1
>
> Attachments: 0001-CAY-1354.patch, 0002-CAY-1354.patch,
> 0003-CAY-1354.patch, 0004-CAY-1354.patch, 0005-CAY-1354.patch,
> 0006-CAY-1354.patch, CAY-1354.patch, CAY-1354.patch, CAY-1354.patch,
> CAY-1354_2.0.patch, 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.
