0

I added a linked fact using:

context.InsertLinked(longOrderKey, longOrder);

At some point later, I want to remove this fact. It's easy for me to construct the key without having the record:

var longOrderKey = (managedAccount.AccountId, PositionType.Long, fungible.FungibleId);

So why do I need the record when removing a linked fact using the method:

context.RetractLinked(longOrderKey, longOrder);

Why can't this method just use the longOrderKey? What if I don't have the 'longOrder' record. Do I really need to look it up before I can remove it?

Quark Soup
  • 4,272
  • 3
  • 42
  • 74

1 Answers1

1

Linked facts are tied to an activation that created them. The purpose of the key is to be able to identify the specific fact if the activation produced more than one linked fact. If you are inserting just one linked fact in the RHS of a rule, you can really set the key to anything, e.g. "1"; if you were to insert two facts, you could set keys to "1" and "2", and so on. In essence, the key is to identify the linked fact within the activation. The fact itself is needed, so that the engine can find the corresponding entries in the working memory. Much like ISession.Retract requires the fact object, so that it can find it in the working memory. Another point is that in most scenarios you should not need to retract the linked facts as they would get retracted automatically, once the activation gets deleted (i.e. the conditions that created the activation become false).

Sergiy Nikolayev
  • 702
  • 4
  • 13
  • If the key uniquely identifies the linked fact, then why do I need to supply that linked fact? This object is analogous to a Dictionary, you only need the key to delete an element from a dictionary. – Quark Soup Sep 08 '21 at 12:51
  • Key here is only required to be unique within the context of this particular rule action. It is not the key that uniquely identifies the object, even though that's how you generated it in your example. It is the object (fact) itself that uniquely identifies the fact through equality comparison. – Sergiy Nikolayev Sep 22 '21 at 01:34
  • That's very useful. – Quark Soup Sep 24 '21 at 13:46