You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/10/17 22:52:38 UTC
[jira] Created: (DERBY-1974) Junit tests that require SQL
authorization mode should use a different database to the default one.
Junit tests that require SQL authorization mode should use a different database to the default one.
---------------------------------------------------------------------------------------------------
Key: DERBY-1974
URL: http://issues.apache.org/jira/browse/DERBY-1974
Project: Derby
Issue Type: Bug
Components: Test
Affects Versions: 10.3.0.0
Reporter: Daniel John Debrunner
Since databases are re-used in the JUnit world having a single database for the two modes does not work.
Not sure if there are any tests that need this yet. SQLAuthorizationPropTest actually tests setting the property so it really needs its own database (I think).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-1974) Junit tests that require SQL
authorization mode should use a different database to the default one.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1974?page=all ]
Daniel John Debrunner closed DERBY-1974.
----------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
Added TestConfiguration.sqlAuthorizationDecorator() to switch to a database that is in SQL authorization mode.
> Junit tests that require SQL authorization mode should use a different database to the default one.
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-1974
> URL: http://issues.apache.org/jira/browse/DERBY-1974
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Fix For: 10.3.0.0
>
>
> Since databases are re-used in the JUnit world having a single database for the two modes does not work.
> Not sure if there are any tests that need this yet. SQLAuthorizationPropTest actually tests setting the property so it really needs its own database (I think).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-1974) Junit tests that require SQL
authorization mode should use a different database to the default one.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1974?page=all ]
Daniel John Debrunner reassigned DERBY-1974:
--------------------------------------------
Assignee: Daniel John Debrunner
> Junit tests that require SQL authorization mode should use a different database to the default one.
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-1974
> URL: http://issues.apache.org/jira/browse/DERBY-1974
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
>
> Since databases are re-used in the JUnit world having a single database for the two modes does not work.
> Not sure if there are any tests that need this yet. SQLAuthorizationPropTest actually tests setting the property so it really needs its own database (I think).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira