<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:34:00 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INSTRM-1305] rename sps_sequence to iic_sequence in opdb</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1305</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;fps command are now (almost) available through iic and follow the same logic(resources allocation, same opdb table...etc) as the sps ones.&lt;br/&gt;
But the opdb sequencing table are still &quot;sps-oriented&quot;.&lt;br/&gt;
I see two problems :&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;renaming sps_sequence -&amp;gt; iic_sequence&lt;/li&gt;
	&lt;li&gt;changing some external constraints in visit_set table, which currently &lt;b&gt;only&lt;/b&gt; expect sps_visit&lt;/li&gt;
&lt;/ul&gt;


&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;class visit_set(Base):
    __tablename__ = &apos;visit_set&apos;

    pfs_visit_id = Column(Integer, ForeignKey(&apos;sps_visit.pfs_visit_id&apos;), primary_key=True, unique=True, autoincrement=False)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="16907">INSTRM-1305</key>
            <summary>rename sps_sequence to iic_sequence in opdb</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="kiyoto.yabe">Kiyoto Yabe</assignee>
                                    <reporter username="arnaud.lefur">arnaud.lefur</reporter>
                        <labels>
                            <label>SPS</label>
                    </labels>
                <created>Thu, 24 Jun 2021 12:26:23 +0000</created>
                <updated>Wed, 14 Jul 2021 22:57:41 +0000</updated>
                            <resolved>Wed, 14 Jul 2021 22:57:41 +0000</resolved>
                                                                    <component>spt_operational_database</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="21598" author="kiyoto.yabe" created="Tue, 29 Jun 2021 07:44:38 +0000"  >&lt;p&gt;So, ForeignKey(&apos;sps_visit.pfs_visit_id&apos;) should be&#160;ForeignKey(&apos;pfs_visit.pfs_visit_id&apos;), right?&#160;&lt;/p&gt;

&lt;p&gt;And, according to the conversation in &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-1291&quot; title=&quot;Create visit_set and sps_sequence rows as soon as practical.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-1291&quot;&gt;&lt;del&gt;INSTRM-1291&lt;/del&gt;&lt;/a&gt;&#160;, 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)&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="16894">INSTRM-1296</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|zzs8eg:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>