/ doc / DocFrag / ARCCore.PRich / Description

Description

Edit keys at this level only

= Fully flexible storage. Can store anything. Typical inherited for entity representations like 'Customer' or 'Order'.0x000D0x000A0x000D0x000APRich = rich property. Rich in the sense that it can store a wide amount of information, including metadata.0x000D0x000A0x000D0x000AInherently not thread-safe due to using Dictionary and not ConcurrentDictionary as storage.0x000D0x000ASee tips about locking in documentation for -OutsideLocalReceiver- and some practical code in -ARCDoc-0x000D0x000A0x000D0x000ASee -PConcurrent- for a (somewhat more) thread-safe alternative.0x000D0x000ASee -PExact- for a more memory efficient alternative (typically used to store entities like 'Customer', 'Product', 'Order' and so on).0x000D0x000ASee -PValue- for how single property values are stored (without metadata), like customer's 'FirstName' and 'LastName'.0x000D0x000A0x000D0x000AProbably suitable when you want full flexibility about which metadata to store (see -PP-) and / or want to store child properties.0x000D0x000AMost probably the one to use for 'ordinary' entities like 'Customer', 'Product', 'Order' and so on (including the collections of such entities), whereas -PValue- is often used for single values for these instances (like 'FirstName', 'Price' and so on).0x000D0x000A0x000D0x000AAn instance of this class can also be used as the single total in-memory data storage in your application, that is, as the dataStorage parameter to -ParseAndStore-.0x000D0x000A0x000D0x000A

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

Generated 2025-07-29 02:44:31.084 UTC