You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Evgeny Ryabitskiy (JIRA)" <ji...@apache.org> on 2010/06/21 11:34:23 UTC
[jira] Commented: (CAY-1451) Oracle specific type support for
cayenne 3
[ https://issues.apache.org/jira/browse/CAY-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880761#action_12880761 ]
Evgeny Ryabitskiy commented on CAY-1451:
----------------------------------------
Actually it's all was fixed in CAY-1354
Where I unified Type Mapping for all Supported DBs.
Fix from CAY-1354 has handle all problems solved in CAY-1323 and CAY-1336 and lot's of others.
So... I'm even going to clean out this handlers from 3.1 as useless.
What I am going to say that this problem is solved in 3.0.
Does your Task based on some tests or just JIRA issues analyze? If it was tests: show logs and examples to simulate problem.
> Oracle specific type support for cayenne 3
> ------------------------------------------
>
> Key: CAY-1451
> URL: https://issues.apache.org/jira/browse/CAY-1451
> Project: Cayenne
> Issue Type: Task
> Components: Core Library
> Affects Versions: 3.0
> Reporter: Frank Zhu
> Fix For: 3.0.1
>
> Attachments: cayenne3.01.patch
>
>
> The cayenne version 3 release doesn't support cayenne native type well. Fixed version only apply to version 3.1
> CAY-1323 oracle.sql.TIMESTAMP in Result of query
> CAY-1336 Oracle specific type support (oracle.sql.*), add handlers.
> Since version 3.1 will deprecate a few methods and move some package around, it is necessary to provide support for oracle in the version 3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.