<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Question on ACT_RU_IDENTITYLINK for DBA adding constraints and indexes in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/question-on-act-ru-identitylink-for-dba-adding-constraints-and/m-p/232380#M185510</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;1) Is it valid to say, ACT_RU_IDENTITYLINK rows will have "either" a user_id or a group_id, but never both?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, for the default out of the box logic that is the case indeed. Custom logic could do that, though.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Again, same story. Out of the box, not. But there are use cases where people update the identity links dynamically and then this rev column is important for detecting concurrent changes.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 25 Mar 2016 15:07:56 GMT</pubDate>
    <dc:creator>jbarrez</dc:creator>
    <dc:date>2016-03-25T15:07:56Z</dc:date>
    <item>
      <title>Question on ACT_RU_IDENTITYLINK for DBA adding constraints and indexes</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/question-on-act-ru-identitylink-for-dba-adding-constraints-and/m-p/232378#M185508</link>
      <description>Hi!My DBA is adding more constraints and indexes to the standard postgresql scripts.Is it valid to say, ACT_RU_IDENTITYLINK rows will have "either" a user_id or a group_id, but never both?Here is an example, our DBA wants to add:===============================alter table act_ru_identitylink add cons</description>
      <pubDate>Mon, 21 Mar 2016 16:50:07 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/question-on-act-ru-identitylink-for-dba-adding-constraints-and/m-p/232378#M185508</guid>
      <dc:creator>jwestra</dc:creator>
      <dc:date>2016-03-21T16:50:07Z</dc:date>
    </item>
    <item>
      <title>Re: Question on ACT_RU_IDENTITYLINK for DBA adding constraints and indexes</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/question-on-act-ru-identitylink-for-dba-adding-constraints-and/m-p/232379#M185509</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;BUMP&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Mar 2016 23:48:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/question-on-act-ru-identitylink-for-dba-adding-constraints-and/m-p/232379#M185509</guid>
      <dc:creator>jwestra</dc:creator>
      <dc:date>2016-03-23T23:48:00Z</dc:date>
    </item>
    <item>
      <title>Re: Question on ACT_RU_IDENTITYLINK for DBA adding constraints and indexes</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/question-on-act-ru-identitylink-for-dba-adding-constraints-and/m-p/232380#M185510</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;1) Is it valid to say, ACT_RU_IDENTITYLINK rows will have "either" a user_id or a group_id, but never both?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, for the default out of the box logic that is the case indeed. Custom logic could do that, though.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Again, same story. Out of the box, not. But there are use cases where people update the identity links dynamically and then this rev column is important for detecting concurrent changes.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2016 15:07:56 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/question-on-act-ru-identitylink-for-dba-adding-constraints-and/m-p/232380#M185510</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2016-03-25T15:07:56Z</dc:date>
    </item>
  </channel>
</rss>

