You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Milosz Tylenda (JIRA)" <ji...@apache.org> on 2009/02/21 10:40:01 UTC
[jira] Created: (OPENJPA-934) Oversight in TestSequenceGenerator
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
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.
[jira] Assigned: (OPENJPA-934) Oversight in TestSequenceGenerator
Posted by "Jeremy Bauer (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (OPENJPA-934) Oversight in TestSequenceGenerator
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-934:
---------------------------------
Fix Version/s: (was: 2.0.0)
2.0.0-M3
> 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-M2
> Reporter: Milosz Tylenda
> Assignee: Jeremy Bauer
> Priority: Trivial
> Fix For: 2.0.0-M3
>
>
> 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.
[jira] Resolved: (OPENJPA-934) Oversight in TestSequenceGenerator
Posted by "Jeremy Bauer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Bauer resolved OPENJPA-934.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
> 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-M2
> Reporter: Milosz Tylenda
> Assignee: Jeremy Bauer
> Priority: Trivial
> Fix For: 2.0.0
>
>
> 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.