[#INSTRM-1352] Some fix and cleanups of `pfsDesign` and `pfsConfig` table

[INSTRM-1352] Some fix and cleanups of `pfsDesign` and `pfsConfig` table Created: 09/Sep/21 Updated: 22/Oct/21 Resolved: 22/Oct/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:

Kiyoto Yabe

Assignee:

Kiyoto Yabe

Resolution:

Done

Votes:

Labels:

EngRun, opDB

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Issue Links:

Blocks
blocks	~~INSTRM-1348~~	Ingest pfsDesign/pfsConfig files to opDB	Done

Story Points:

Sprint:

EngRun03, EngRun3Cleanup

Description

During some tests in ~~INSTRM-1348~~, I found some fix and cleanups (e.g., remove auto-incremented `pfs_config_id` for a primary key and use {`pfs_design_id`, `visit0`} instead, remove some ForeignKey constraints, etc.) are needed.

Comments

Comment by Kiyoto Yabe [ 05/Oct/21 ]

Currently, target information such as obj_id/cat_id/coordinates etc. in `pfs_design_fiber` table because those are included in `pfsDesign` file. Do we want to remove them and refer to somewhere (e.g. targetDB)?

Comment by Kiyoto Yabe [ 22/Oct/21 ]

I will close this ticket and file a new one if there are further fixes needed.

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

[INSTRM-1352] Some fix and cleanups of `pfsDesign` and `pfsConfig` table Created: 09/Sep/21 Updated: 22/Oct/21 Resolved: 22/Oct/21