hermes - 💡(How to fix) Fix [Feature Request] Support profile isolation via separate MySQL databases in memory-tencentdb

Problem

The memory-tencentdb plugin currently supports only a single MySQL database + single data directory. When Hermes runs with multiple profiles, each profile may want to use memory-tencentdb but they end up sharing the same database and gateway, causing port conflicts and data mixing.

Current workaround

Users must either:

• Use different memory providers for different profiles
• Run multiple gateway processes on different ports (resource-heavy)
• Manually manage data directory isolation

Proposed solution: Per-profile MySQL database isolation

Instead of one database per Hermes installation, use one database per profile:

• Single gateway process: One Node gateway process serves all profiles on a single port
• MySQL database per profile: memory_<profile> (e.g., memory_main, memory_tinka)
• Profile-aware connection string: Gateway reads HERRMES_PROFILE env var to select database
• Backward compatible: Default profile uses existing database name

Implementation sketch

1. Gateway startup: detect HERMES_PROFILE env var (defaults to main)
2. On connect: use memory_<profile> as the MySQL database name
3. Each profile's L1/L2/L3 data lives in its own database — fully isolated
4. No port juggling needed — single gateway, single port

Benefits

Alternative considered (per-profile gateway)

Separate gateway per profile with different ports. More resource-intensive and harder to manage — the per-database approach above is cleaner.

Use case example

• Main profile: connects to MySQL database memory_main
• Profile "tinka": connects to MySQL database memory_tinka

Both share the same gateway binary and port, but are fully isolated at the database level.