Uploaded image for project: 'In-Portal CMS'
  1. In-Portal CMS
  2. INP-528

ResourceId field refactoring

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: New
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 5.0.3-B1
    • Fix Version/s: None
    • Component/s: Optimization
    • Labels:
      None
    • External issue URL:
    • Additional information:
      Hide

      Places, where ResourceId field is defined:

      int_Category.ResourceId
      int_Link.ResourceId
      int_News.ResourceId
      int_PortalGroup.ResourceId - possible, that it's not used
      int_PortalUser.ResourceId
      int_Posting.ResourceId - possible, that it's not used
      int_Products.ResourceId
      int_Topic.ResourceId

      Places, where ResourceId field is used:

      int_AffiliatePlansItems.ItemResourceId
      int_CategoryCustomData.ResourceId
      int_CategoryItems.ItemResourceId
      int_Favorites.ResourceId
      int_Images.ResourceId
      int_ItemFiles.ResourceId
      int_LinkCustomData.ResourceId
      int_LinkVisits.ResourceId
      int_Listings.ItemResourceId
      int_NewsCustomData.ResourceId
      int_PortalUserCustomData.ResourceId
      int_ProductsCouponItems.ItemResourceId
      int_ProductsCustomData.ResourceId
      int_ProductsDiscountItems.ItemResourceId
      int_RelatedSearches.ResourceId
      int_SpamControl.ItemResourceId
      int_TopicCustomData.ResourceId
      int_AffiliatePlansItems.ItemResourceId

      Show
      Places, where ResourceId field is defined: int_Category.ResourceId int_Link.ResourceId int_News.ResourceId int_PortalGroup.ResourceId - possible, that it's not used int_PortalUser.ResourceId int_Posting.ResourceId - possible, that it's not used int_Products.ResourceId int_Topic.ResourceId Places, where ResourceId field is used: int_AffiliatePlansItems.ItemResourceId int_CategoryCustomData.ResourceId int_CategoryItems.ItemResourceId int_Favorites.ResourceId int_Images.ResourceId int_ItemFiles.ResourceId int_LinkCustomData.ResourceId int_LinkVisits.ResourceId int_Listings.ItemResourceId int_NewsCustomData.ResourceId int_PortalUserCustomData.ResourceId int_ProductsCouponItems.ItemResourceId int_ProductsCustomData.ResourceId int_ProductsDiscountItems.ItemResourceId int_RelatedSearches.ResourceId int_SpamControl.ItemResourceId int_TopicCustomData.ResourceId int_AffiliatePlansItems.ItemResourceId
    • Story Points:
      3
    • External issue ID:
      669
    • Copy Issue Key:
    • Patch Instructions:

      Patches must be submitted through Phabricator.

      Description

      I propose to refactor implementation of ResourceId field. Now ResourceId field is unique for all database. We should add Prefix column, where ResourceId column is being used (not in main tables of course) and store ID of item instead of it's ResourceId (category item review system is using this for now using ItemId and ItemPrefix fields). This will be faster to query and use. For example we don't need additional database query to get actual item's ID by it's resource id.

        Attachments

          Issue Links

          mentioned in

          Page Loading...

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                alex Alex
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: