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

Posted to dev@openjpa.apache.org by "Diddle (JIRA)" <ji...@apache.org> on 2010/05/08 21:24:47 UTC

[jira] Updated: (OPENJPA-1655) @OrderBy on a Timestamp field fails with Postgres jdbc4 driver

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

Diddle updated OPENJPA-1655:
----------------------------

    Environment: Tomcat 5.5, Eclipse J2ee preview jdbc4 Postgres 8.4, Java SE Runtime Environment (build 1.6.0_18-b07)  (was: Tomcat 5.5, Eclipse J2ee preview jdbc4 Postgres 8.4)

> @OrderBy on a Timestamp field fails with Postgres jdbc4 driver
> --------------------------------------------------------------
>
>                 Key: OPENJPA-1655
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1655
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 1.2.2
>         Environment: Tomcat 5.5, Eclipse J2ee preview jdbc4 Postgres 8.4, Java SE Runtime Environment (build 1.6.0_18-b07)
>            Reporter: Diddle
>            Priority: Minor
>
> It doesn't matter if use @OrderBy on a Timestamp field. ASC DESC, it's all the same.
> It seems to be sorting it on another field altogether. It's not the id order.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.