Apparently, you have autocompile enabled for the CSP application: Automatic and Manual Page Compilation
And also check the parameter Recurse

You can still avoid code duplication.
To do this, you need to make a function, and already use it in query.

For example:

/// Linked Funds via Person->Fund link
ClassMethod LinkedFundsByPerson(personId As %Integer) As %Boolean [ SqlName = CUSTOM_MyQuery, SqlProc ]
{
  &sql(SELECT NULL FROM QUASAR_Core_Client.Client AS Client
      INNER JOIN QUASAR_KYC_Fund.Fund AS Fund ON Client.Number=Fund.InternalReference
      LEFT JOIN QUASAR_GDPR_Close_Fund.FundClosure As FundClosure ON Client.Number=FundClosure.ID
    WHERE Client.ClientMarketIndicator='C'
    AND Client.Number IN
    (
    SELECT Client
    FROM QUASAR_KYC_Person.FundLink
    WHERE Person->InternalReference=:personId
    )
  )
  QUIT ''%ROWCOUNT
}

SELECT *
FROM TableA
WHERE CUSTOM_MyQuery(ID)>0

You can't pass IDENTIFIER to class query, but only LITERALS. This is akin to error 5262:

Cannot project query with parameters '%1' as view

Here is a simple demo of this issue:

Class dc.test Extends %Persistent
{

Property p As %Integer;

Query LinkedFundsByPerson(p As %Integer) As %SQLQuery(ROWSPEC = "p:%Integer") [ SqlName = CUSTOM_MyQuery, SqlProc ]
{
SELECT p FROM dc.test
where ID IN
(
SELECT ID
FROM dc.test
WHERE p=:p
)
}

ClassMethod test()
{
  &sql(SELECT * FROM dc.test WHERE EXISTS (SELECT * FROM dc.CUSTOM_MyQuery(ID)))
}

}

By the way, InterSystems employees have already given examples of undocumented code here, which can be found independently in %SYS:

• https://community.intersystems.com/post/there-way-get-internal-private-p...
• https://community.intersystems.com/post/what-best-way-serialize-objectli...

If you look at a modern version of Caché or IRIS you'll find that ^%SYS.SECURITY is hidden.

What does the source code of ^%SYS.SECURITY have to do with it? The fact that it is hidden does not play any role here.

Take a look at the code %CSP.Portal.Home:%OnPreHTTP()

I keep my promise (yes, it wasn't an April Fool's joke ;)

• The first way is associated with a dummy field for the sake of being able to override the final BuildValueArray method and avoid the following error

  ERROR #5272: Can't change final 'Method' : 'BuildValueArray')

  Class rcc.IC.ItemList Extends (%Persistent, %Populate) [ Final ]
  {
  
  Index xitmp On (ItemsP(KEYS), ItemsP(ELEMENTS));
  
  Property Company As %String [ Required ];
  
  Property Region As list Of %String(COLLATION = "EXACT", POPSPEC = ":4", VALUELIST = ",US,CD,MX,EU,JP,AU,ZA") [ Required ];
  
  Property Items As list Of rcc.IC.serItem(POPSPEC = ":4") [ Required ];
  
  Property ItemsP As %String(COLLATION = "EXACT") [ Calculated, Private, ReadOnly, Required, SqlComputeCode = {s {*} = {Items}}, SqlComputed ];
  
  ClassMethod ItemsPBuildValueArray(
    value,
    ByRef array) As %Status
  {
    s ptr=0
    while $listnext(value,ptr,val){
      s v=$li(val,1),
        array($li(v,1))="Subject",
        array($li(v,2))="Change",
        array($li(v,3))="Color"
    }
    q $$$OK
  }
  
  }

  select count(ID) from rcc_IC.ItemList where FOR SOME %ELEMENT(ItemsP) (%key in ('blue','yellow') and %value='Color')

  or if need to find values in any fields

  select count(ID) from rcc_IC.ItemList where FOR SOME %ELEMENT(ItemsP) (%key in ('blue','yellow'))

  For the sake of speed, you can store in the index not all the fields of the serial class, i.e.:

  Index xitmp On ItemsP(KEYS);
  
  ClassMethod ItemsPBuildValueArray(
    value,
    ByRef array) As %Status
  {
    s ptr=0
    while $listnext(value,ptr,val){
      s v=$li(val,1),
        array($li(v,3))="" ; only Color
    }
    q $$$OK
  }

  select count(ID) from rcc_IC.ItemList where FOR SOME %ELEMENT(ItemsP) (%key in ('blue','yellow'))

  You can also add more dummy fields and accordingly indexes to cover all possible queries.

---

• The second way involves changing the storage and creating a virtual table

  Class rcc.IC.ItemList Extends (%Persistent, %Populate) [ Final ]
  {
  
  Index xitm On Items(ELEMENTS).Color;
  
  Index xitm1 On (Items(ELEMENTS).Color, Items(KEYS));
  
  Property Company As %String [ Required ];
  
  Property Region As list Of %String(COLLATION = "EXACT", POPSPEC = ":4", VALUELIST = ",US,CD,MX,EU,JP,AU,ZA") [ Required ];
  
  Property Items As list Of rcc.IC.serItem(POPSPEC = ":4", STORAGEDEFAULT = "array") [ Required ];
  
  }

  select count(distinct ID) from rcc_IC.ItemList where ItemList_Items->Items_Color in ('blue','yellow') -- index "xitm1" is used

  or even faster

  select count(ID) from rcc_IC.ItemList where FOR SOME %ELEMENT(Items) (%Value in ('blue','yellow')) -- index "xitm" is used

  Of course, the data can be accessed from both tables, just do not forget about SetCollectionProjection GetCollectionProjection (for more information, see my article SQL index for array property elements)

It is better to check this with your license, as it is likely that some of its options, such as Web Add-on, may affect this (see $SYSTEM.License.PublicWebAppUser).

Hi Robert.

I also got carried away with this question and found two more ways to use indexes for a list of serial objects, and you can explicitly specify specific fields in the query, rather than $list (%Value,3).

The speed may be not always the best, but I did the best I could. I tested on Caché (perhaps something has been improved in IRIS in this regard?)

If you're interested, I can share it.

See Working with Streams

Topicstarter indicated Caché 2018.1, which is no longer being developed so not may change in the future (not counting security patches)

Unfortunately, %INLIST does not use indexes (at least it was in Caché, I do not know how it is now in IRIS), which I made a note about in my article.

$LISTFIND certainly does its job well, but there is a better solution.

As the data grows, the search speed will drop, since this solution does not use indexes in any way.
Therefore, the best solution is to use the predicate FOR SOME %ELEMENT.

For more details with examples, see one of my articles: SQL Performance Resources (item k. Indexing of non-atomic attributes)