db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
Date Thu, 07 Sep 2006 23:23:25 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]

Deepa Remesh updated DERBY-1522:

    Attachment: derby1522_v2.diff

Attaching a patch 'derby1522_v2.diff. It includes a JUnit test for testing the switch to SQL
standard authorization. It tests following:

1. grant/revoke is not available if derby.database.sqlAuthorization property is not set.
2. grant/revoke is available when derby.database.sqlAuthorization is set to true.
3. Once derby.database.sqlAuthorization is set to true, it cannot be set to any other value.

This patch also modifies DatabasePropertyTestSetup.tearDown method. The tearDown method resets
the property values to old values. It will now ignore exceptions when property reset is not
supported. I am including this small change in the above patch. (I had opened DERBY-1827 for
the issue with tearDown method. ). I am using TestUtil.getConnection method to shutdown the
database. I have opened DERBY-1826 to add methods to Derby's JUnit classes for shutdown.

Since the new test internally sets derby.database.sqlAuthorization property which cannot be
reset, it may cause problems in tests which share the same database and rely on the value
of this property. I am checking it does not affect any current tests by running derbyall.
I have successfully run the new JUnit test standalone and as part of harness using Sun JDK
1.4.2 on Windows XP.  Please take a look at this patch and provide feedback.

> 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:
>            Reporter: Mamta A. Satoor
>         Assigned To: Deepa Remesh
>             Fix For:
>         Attachments: d1522_junit_v1.diff, d1522_junit_v1.status, derby1522_v2.diff, derby1522_v2.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


View raw message