[
https://issues.apache.org/jira/browse/CAY-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797100#action_12797100
]
Evgeny Ryabitskiy edited comment on CAY-1354 at 1/6/10 12:45 PM:
-----------------------------------------------------------------
Yeah.. so I think that 2 issues was fixed in CAY-1259 by me. And now it is
working.
Actually I wasn't first who pointed on wrong lines here CAY-1052 but solution
wasn't best I think...
Also all tests are passed. My patch didn't broke anything... or we have not so
good coverage and tests didn't catch regression....
I don't have Postgress so I can't check CAY-1052 but I'm sure for 95% that it
is not related to my changes.
was (Author: apparition):
Yeah.. so I think that 2 issues was fixed in CAY-1259 by me. And now it is
working.
Actually I wasn't first who pointed on wrong lines here CAY-1052 but solution
wasn't best I think...
Also all tests are passed. My patch didn't broke anything... or we have not so
good coverage and tests didn't catch regression....
> 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: CAY-1354.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.
