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"

User Story #10232 (new)

Opened 12 years ago

Dataset:Image ONE-to-many

Reported by: wmoore Owned by:
Priority: major Milestone: Unscheduled
Component: General Keywords: n.a.
Cc: jamoore, cxallan, jburel Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.


Images can be in multiple Datasets for historical reasons. This is not a feature that is used by anyone now, as far as I know. But it creates a LOT of extra work for developers and users are confused when they come across this.

We could add "unique" to child in the Dataset-Image-Link table, so there's only 1 link per image. This wouldn't need a change to the Model or any queries.
We'd need a DB upgrade script so admins could choose (or just randomly pick) a parent for each Image that is currently in 2 Datasets (probably not very many).

Many existing calls, E.g. BlitzGateway? Image.getParent() already assume a single parent and would continue to work with no changes.

All the above also applies to Project:Dataset links too.

Change History (0)

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.64508 sec.)

We're Hiring!