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 "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2006/09/06 21:13:23 UTC
[jira] Updated: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Deepa Remesh updated DERBY-1522:
--------------------------------
Attachment: d1522_junit_v1.diff
d1522_junit_v1.status
I was trying to write a JUnit test case for this issue. The attached patch 'd1522_junit_v1.diff' (which is not for commit) covers the first part of the test. It is a small JUnit test which just checks grant/revoke is not available when sql authorization property is not set.
Next, I would like to set this property to true and then check grant/revoke is supported. I see that DatabasePropertyTestSetup has some methods to set database properties. I tried this but for the sql authorization property to take effect, we would need to shutdown and reconnect to the database. Shutdown can be done using existing TestUtil method but I wanted to check if there is something for this in JUnit helper classes. Also, is it possible to use DatabasePropertyTestSetup to set a property only for a particular test method?
This is my first attempt in writing a JUnit test and would appreciate help in how to proceed with this.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
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