You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Jeremy Bauer (JIRA)" <ji...@apache.org> on 2009/02/23 16:30:02 UTC

[jira] Assigned: (OPENJPA-934) Oversight in TestSequenceGenerator

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

Jeremy Bauer reassigned OPENJPA-934:
------------------------------------

    Assignee: Jeremy Bauer

Thanks, Milosz.  My bad.  Pinaki also pointed out this bug a short while ago.  I'll make the correction.

> Oversight in TestSequenceGenerator
> ----------------------------------
>
>                 Key: OPENJPA-934
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-934
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.0.0
>            Reporter: Milosz Tylenda
>            Assignee: Jeremy Bauer
>            Priority: Trivial
>
> There is a small oversight in TestSequenceGenerator which results in the test being run on a database without sequences and not being run on a database with sequences.
> The snippet:
>         try {
>             enabled =
>                 ((JDBCConfiguration) emf.getConfiguration())
>                     .getDBDictionaryInstance().nextSequenceQuery == null;
>         } catch (Throwable t) {
>             enabled = false;
>         }
> should read:
>         try {
>             enabled =
>                 ((JDBCConfiguration) emf.getConfiguration())
>                     .getDBDictionaryInstance().nextSequenceQuery != null;
>         } catch (Throwable t) {
>             enabled = false;
>         }

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