catalyst-cache
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseHow It Works
工作原理
- Get Segment ID — Use MCP () if available; otherwise retrieve it from the console or
CatalystbyZoho_List_Cache_Segments..catalystrc - Load — for SDK operations, TTL limits (48 hr max), and the
references/cache-basics.md/segment.delete()gotchas.segment.update() - String values only — All cache values are strings. Always before
JSON.stringifyandputafterJSON.parse.get - TTL behavior — resets TTL to the new value, not adds to existing.
segment.update()returnssegment.delete()(not an error) if the key is missing.null
- 获取Segment ID — 如果可用,请使用MCP();否则从控制台或
CatalystbyZoho_List_Cache_Segments文件中获取。.catalystrc - 加载— 了解SDK操作、TTL限制(最长48小时)以及
references/cache-basics.md/segment.delete()的注意事项。segment.update() - 仅支持字符串值 — 所有缓存值均为字符串。执行操作前务必使用
put,执行JSON.stringify操作后使用get解析。JSON.parse - TTL行为 — 会将TTL重置为新值,而非在原有基础上累加。如果密钥不存在,
segment.update()返回segment.delete()(不会报错)。null
Triggers
触发场景
Use this skill for: "Cache", "cache segment", "cache key", "cache value", "TTL", "in-memory store", , , , "session data", "temporary data Catalyst", "cache vs Data Store", or "48-hour cache".
segment.getsegment.putsegment.delete使用此技能处理以下相关问题:"Cache"、"cache segment"、"cache key"、"cache value"、"TTL"、"in-memory store"、、、、"session data"、"temporary data Catalyst"、"cache vs Data Store"或"48-hour cache"。
segment.getsegment.putsegment.deleteReferences
参考资料
| Reference | Load when the query is about… |
|---|---|
| SDK operations (get, put, delete, update), Segment ID, 48hr TTL max, string-only values, segment.delete() null gotcha, segment.update() TTL gotcha |
| 参考资料 | 查询以下内容时加载… |
|---|---|
| SDK操作(get、put、delete、update)、Segment ID、最长48小时TTL、仅支持字符串值、segment.delete()返回null的注意事项、segment.update()的TTL注意事项 |