https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/OBSPROC-38 PFS observation processing/procedure <p>(proposal_id, ob_code) pair must be unique to track the progress. It will need to be implemented in the target table of targetdb.</p> OBSPROC-38

add a unique constraint of (proposal_id, ob_code) in the target table

Task Normal Done Done monodera monodera targetDB Thu, 20 Apr 2023 02:44:27 +0000 Thu, 20 Apr 2023 10:53:54 +0000 Thu, 20 Apr 2023 10:53:54 +0000 ets_target_database 0 1 <p>I modified code and tried to update the schema with alembic. The update script returned errors by detecting duplicates for the unique constraint. It seems some objects have been inserted twice.</p> <p> </p> <blockquote><p>targetdb_comm2022may=# SELECT proposal_id, ob_code, ra, dec, count<img class="emoticon" src="https://pfspipe.ipmu.jp/jira/images/icons/emoticons/star_yellow.png" height="16" width="16" align="absmiddle" alt="" border="0"/> FROM target GROUP BY proposal_id, ob_code, ra, dec HAVING count<img class="emoticon" src="https://pfspipe.ipmu.jp/jira/images/icons/emoticons/star_yellow.png" height="16" width="16" align="absmiddle" alt="" border="0"/> &gt; 1;<br/> proposal_id | ob_code | ra | dec | count<br/> ------------<del>+<ins></del>-----------------------------------------<del></ins>+</del>-------------------<br/> S23A-EN16 | r_0_ishigaki_ga_2023feb | 204.98178239 | 28.2770517 | 2<br/> S23A-EN16 | r_10000_ishigaki_ga_2023feb | 205.49925232 | 28.39503098 | 2<br/> S23A-EN16 | r_10001_ishigaki_ga_2023feb | 205.49926758 | 28.36640549 | 2<br/> S23A-EN16 | r_10002_ishigaki_ga_2023feb | 205.49926758 | 28.35559845 | 2<br/> S23A-EN16 | r_10003_ishigaki_ga_2023feb | 205.49928284 | 28.3361454 | 2<br/> S23A-EN16 | r_10004_ishigaki_ga_2023feb | 205.4992981 | 28.33244896 | 2<br/> S23A-EN16 | r_10005_ishigaki_ga_2023feb | 205.4992981 | 28.33455276 | 2<br/> S23A-EN16 | r_10006_ishigaki_ga_2023feb | 205.4992981 | 28.25308037 | 2<br/> S23A-EN16 | r_10007_ishigaki_ga_2023feb | 205.49931335 | 28.39699745 | 2<br/> S23A-EN16 | r_10008_ishigaki_ga_2023feb | 205.49932861 | 28.40284538 | 2<br/> S23A-EN16 | r_10009_ishigaki_ga_2023feb | 205.49932861 | 28.39302063 | 2<br/> S23A-EN16 | r_1000_ishigaki_ga_2023feb | 205.69470905 | 28.42560075 | 2<br/> S23A-EN16 | r_10010_ishigaki_ga_2023feb | 205.49934387 | 28.38490105 | 2<br/> S23A-EN16 | r_10011_ishigaki_ga_2023feb | 205.49935913 | 28.30970573 | 2<br/> S23A-EN16 | r_10012_ishigaki_ga_2023feb | 205.49935913 | 28.3936615 | 2<br/> S23A-EN16 | r_10013_ishigaki_ga_2023feb | 205.49937439 | 28.31223869 | 2<br/> S23A-EN16 | r_10014_ishigaki_ga_2023feb | 205.49937439 | 28.31671143 | 2</p></blockquote> <p> </p> <p>Perhaps, it will be safe to delete one of duplicated rows, but wait for a bit.</p> <p>Using the following queries, I deleted one of two entries of duplicates. Then the alembic update succeeded.</p> <blockquote> <p>targetdb_comm2022may=# SELECT ct, count() AS ct_ct FROM (SELECT proposal_id, ob_code, ra, dec, count() AS ct FROM target GROUP BY proposal_id, ob_code, ra, dec HAVING count<img class="emoticon" src="https://pfspipe.ipmu.jp/jira/images/icons/emoticons/star_yellow.png" height="16" width="16" align="absmiddle" alt="" border="0"/> &gt; 1) sub GROUP BY 1 ORDER BY 1;<br/> ct | ct_ct<br/> ---<del>+</del>------<br/> 2 | 97561<br/> (1 row)</p> <p>targetdb_comm2022may=# DELETE FROM target a USING target b WHERE a.target_id &gt; b.target_id AND a.ob_code = b.ob_code;<br/> DELETE 97561</p></blockquote> <p>The database column was updated.</p> Development Epic Link OBSPROC-1 Rank 0|zzswrz: Reviewers monodera