You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by ji...@apache.org on 2004/04/26 17:18:53 UTC

[jira] Created: (DIRRMS-26) Checks constraint on BitPermissionDAO.rename() 

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRRMS-26

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRRMS-26
    Summary: Checks constraint on BitPermissionDAO.rename() 
       Type: Task

     Status: Open
   Priority: Major

    Project: Directory RMS
 Components: 
             Berkeley JE

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Mon, 26 Apr 2004 8:18 AM
    Updated: Mon, 26 Apr 2004 8:18 AM

Description:
I don't think the rename operation currently checks to see if the newName of the permission is already taken.  This must be checked to prevent overwriting the name of another permission and making the permission database inconsistant.



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Closed: (DIRRMS-26) Checks constraint on BitPermissionDAO.rename()

Posted by ji...@apache.org.
Message:

   The following issue has been closed.

   Resolver: Alex Karasulu
       Date: Tue, 27 Apr 2004 1:06 PM

Committed with revision #10322.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRRMS-26

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRRMS-26
    Summary: Checks constraint on BitPermissionDAO.rename()
       Type: Task

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Directory RMS
 Components: 
             Berkeley JE

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Mon, 26 Apr 2004 8:18 AM
    Updated: Tue, 27 Apr 2004 1:06 PM

Description:
I don't think the rename operation currently checks to see if the newName of the permission is already taken.  This must be checked to prevent overwriting the name of another permission and making the permission database inconsistant.



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira