Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #2580 (closed)

Opened 14 years ago

Closed 12 years ago

Possibly remove permissions column from all objects

Reported by: jamoore Owned by:
Priority: major Milestone: OMERO-4.4
Component: ORM Version: n.a.
Keywords: n.a. Cc: cxallan, jburel
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: 2012-03-27 (11)

Description

Since all permissions are now group based we could remove the permissions column. Perhaps rename it flag? Chris also wonders if we could have object.getDetails().getPermissions() return the group value.

Change History (3)

comment:1 Changed 13 years ago by jmoore

Referencing ticket #2568 has changed sprint.

comment:2 Changed 13 years ago by jmoore

Referencing ticket #4891 has changed sprint.

comment:3 Changed 12 years ago by jmoore

  • Milestone changed from Unscheduled to OMERO-Beta4.4
  • Resolution set to wontfix
  • Sprint set to 2012-03-27 (11)
  • Status changed from new to closed

Not doing this for the moment. Until we know that this update-permissions-on-read strategy (see #8277) is going to cover all use cases, it wouldn't be prudent to remove these columns.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.73061 sec.)

© 2000-2014 University of Dundee & Open Microscopy Environment. Creative Commons Attribution 3.0 Unported License
OME source code is available under the GNU General public license or through commercial license from Glencoe Software

We're Hiring!