[INSTRM-1305] rename sps_sequence to iic_sequence in opdb Created: 24/Jun/21  Updated: 15/Jul/21  Resolved: 15/Jul/21

Status: Done
Project: Instrument control development
Component/s: spt_operational_database
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: arnaud.lefur Assignee: Kiyoto Yabe
Resolution: Done Votes: 0
Labels: SPS
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks INSTRM-1296 Add IIC commands for main FPS routines. Done

 Description   

fps command are now (almost) available through iic and follow the same logic(resources allocation, same opdb table...etc) as the sps ones.
But the opdb sequencing table are still "sps-oriented".
I see two problems :

  • renaming sps_sequence -> iic_sequence
  • changing some external constraints in visit_set table, which currently only expect sps_visit
class visit_set(Base):
    __tablename__ = 'visit_set'

    pfs_visit_id = Column(Integer, ForeignKey('sps_visit.pfs_visit_id'), primary_key=True, unique=True, autoincrement=False)


 Comments   
Comment by Kiyoto Yabe [ 29/Jun/21 ]

So, ForeignKey('sps_visit.pfs_visit_id') should be ForeignKey('pfs_visit.pfs_visit_id'), right? 

And, according to the conversation in INSTRM-1291 , do we need to make `visit_set_id` a primary key as well? (a unique constraint for (pfs_visit_id, visit_set_id) should be taken in this case)

Generated at Sat Feb 10 16:33:59 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.