Ticket #288 (closed design issue: fixed)

Opened 11 years ago

Last modified 7 years ago

Cross-release queries

Reported by: jbecla Owned by: jbecla
Priority: normal Milestone:
Component: database Keywords:
Cc: Blocked By:
Blocking: Project: LSST
Version Number:
How to repeat:

not applicable

Description

Question 1: Will we need to ensure object ids for corresponding entries match between different data releases?

Question 2: Will we need to compare different deep detection runs (e.g. with different deblending thresholds)? This was suggested by Andy Becker, 11/30/2007

Change History

comment:1 Changed 11 years ago by TimAxelrod

  • Status changed from new to assigned

comment:2 Changed 11 years ago by jbecla

  • Component changed from unknown to database

comment:3 Changed 11 years ago by jbecla

  • Owner changed from Tim Axelrod to jbecla

comment:4 Changed 11 years ago by jbecla

  • Status changed from assigned to closed
  • Resolution set to fixed

There are more reasons to ensure object ids match between data releases, so the answer is YES, we should support that. See also dbObjectIdSync

comment:5 Changed 7 years ago by robyn

  • Milestone DC3 Design deleted

Milestone DC3 Design deleted

Note: See TracTickets for help on using tickets.