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 #196 (assigned)

Opened 13 years ago

Last modified 11 years ago

Examine redefining the CodomainMapContext types and others as structs

Reported by: jamoore Owned by: cxallan
Priority: minor Milestone: Unscheduled
Component: Model Version: 3.0-M2
Keywords: structs Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

Some of our types like CodomainMapContext? have no real lifecycle (are only linked by a single FK) and don't themselves contain FKs. It would make sense to simplify these. Two current struct like classes can be found in ome.model.internal (Permissions and Details) A more general policy for structs could be useful.

Change History (6)

comment:1 Changed 13 years ago by jmoore

  • Milestone changed from Unscheduled to 3.0-M4

Re-scheduling with #334

comment:2 Changed 13 years ago by jmoore

  • Milestone changed from 3.0-Beta2 to 3.0-Beta3

comment:3 Changed 12 years ago by jmoore

  • Milestone changed from 3.0-Beta3 to 3.0-Beta4

comment:4 Changed 11 years ago by jmoore

  • Owner changed from jmoore to callan

Chris, passing this off to you. You were thinking about re-normalizations. If you need me to do anything at the Hibernate level, let me know.

comment:5 Changed 11 years ago by cxallan

  • Status changed from new to assigned

Pushing to milestone:OMERO-Beta4.1 where we'll be doing a rendering engine review.

comment:6 Changed 11 years ago by cxallan

  • Milestone changed from OMERO-Beta4 to OMERO-Beta4.1
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.81017 sec.)

We're Hiring!