Key-value and cache

Memcached

Memcached is documented around known-key operations and server diagnostics because it has no portable native key browser.

Available for known-key reads; broad enumeration is unavailable12 minDesktop

Prerequisites

  • Install the current DataPad++ desktop pre-release on Windows, macOS, or Linux.
  • Have the endpoint, database file, or cloud account details for a Memcached datastore you are authorized to use. Start with least-privileged, read-only access.
  • Keep an independent backup before enabling edits, administration, restore, or transfer execution.

Connect and run a safe query

  1. 1

    Create the connection

    Open Library, choose Create connection, and select Memcached and a supported Connection method tab.

  2. 2

    Test and save

    Complete the applicable fields and enable Read-only connection. Test connection when available; new local files and pending secondary credential changes must be saved first. Review runtime limitations and warnings.

    Memcached connection setup. The Memcached connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving.
    Memcached connection setup. The Memcached connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving. Open full size
  3. 3

    Open the native explorer

    Use Save Connection, or Create Database and Save Connection for a new local file, then open the Memcached Explorer where supported.

  4. 4

    Select a scope

    Select the database / namespace scope that should be attached to the new tab.

  5. 5

    Run a bounded read

    Open a query tab, paste the bounded read-only sample below, and choose Run or press Ctrl/Cmd+Enter.

    Memcached native workflow. A representative Memcached explorer and bounded read-only workflow. Replace the example objects with names from your datastore.
    Memcached native workflow. A representative Memcached explorer and bounded read-only workflow. Replace the example objects with names from your datastore. Open full size
  6. 6

    Inspect the result

    Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.

  7. 7

    Export when needed

    Export only the required rows after reviewing format, destination, and redaction options.

  8. 8

    Open diagnostics or transfers

    Open Diagnostics or Transfers from the drawer/status bar and treat disabled reasons as capability boundaries, not transient errors.

Connection fields

FieldRequiredPurposeSafe example
NameYesA clear profile name, without credentials.Memcached development
Connection methodYesChoose a supported tab. The fields below apply only to the selected method and deployment.Connection fields / Connection string
EnvironmentNoAttach the intended variable and safety context.Local development
Read-only connectionNoEnable for initial exploration. This does not make pre-release software safe for production workloads.Enabled
Host / PortNoEndpoint for a fields-based connection. Follow the selected deployment and runtime limitations; MongoDB SRV does not use an explicit port.localhost / engine default
Database / default scopeNoInitial scope for browsing, where supported.catalog
Complete connection stringYesRequired in Connection string mode only. Saved unchanged as one vault secret with Save Connection. Blank keeps an existing stored value.Paste your complete provider string; do not share it
UsernameNoAuthentication identity for the selected method.catalog_reader
PasswordNoRequired only when the chosen authentication needs it. Save Connection stores changes; blank preserves an existing value, and Reveal… explicitly discloses it.Stored in the desktop OS vault
ServersNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
ProtocolNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.text / binary
NamespaceNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Connect timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Request timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default

Run the sample query

Memcached read-only example
stats items

Explore and inspect

  • Browse stats, slabs, item classes, settings, connections, cache diagnostics, and known-key action targets instead of fake key lists.
  • Inspect stats tables, slab/item-class rows, setting rows, connection pressure, known-key values, CAS metadata, and raw text responses.

Diagnose, administer, and transfer

  • Review server stats, slabs, item classes, settings, connections, LRU crawler metadata, memory pressure, hit/miss posture, and cache diagnostics.
  • Preview stats reset, flush, LRU crawler metadata dumps, known-key set/touch/increment/decrement/delete, and cache management plans.
  • Import — Live. Memcached transfers only an explicitly selected key. The artifact contains the exact raw value bytes; flags and expiry are explicit protocol inputs. Formats: Raw value bytes (native). Destinations: local file.
  • Export — Live. Memcached transfers only an explicitly selected key. The artifact contains the exact raw value bytes; flags and expiry are explicit protocol inputs. Formats: Raw value bytes (native). Destinations: local file.
  • Backup — Unavailable. This datastore has no supported in-process or server API for a full native backup artifact. Formats: Native managed backup (native). Destinations: cloud uri, server path. Full Memcached backup and restore require excluded vendor tooling or storage-backend access.
  • Restore — Unavailable. This datastore has no supported in-process or server API for a full native backup artifact. Formats: Native managed backup (native). Destinations: cloud uri, server path. Full Memcached backup and restore require excluded vendor tooling or storage-backend access.
Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action.
Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. Open full size

Capabilities and availability

CapabilityStatusNotes
Native explorerAvailableBrowse stats, slabs, item classes, settings, connections, cache diagnostics, and known-key action targets instead of fake key lists.
Read queriesAvailableUse deterministic command IntelliSense for stats, known-key get/gets, CAS reads, set/touch/incr/decr/delete previews, slab/item-class targets, and guarded write snippets.
Inline editingUnavailableUse a reviewed statement or the engine-native tool instead.
Diagnostics / administrationGuardedPreview stats reset, flush, LRU crawler metadata dumps, known-key set/touch/increment/decrement/delete, and cache management plans.
Import / export / transferGuardedAvailability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented.

Safety and limitations

Troubleshooting

SymptomResolution
Test connection fails or times outVerify endpoint, port, TLS mode, proxy settings, service health, firewall rules, and network access. Keep the profile unsaved until the test explains the failure.
Explorer branches are empty or disabledConfirm the selected database / namespace, refresh the branch, and grant the minimum metadata permissions described in the connection warning.
Run, edit, admin, or transfer is disabledRead the visible disabled reason. Select a compatible target, turn off read-only only when authorized, or use the documented preview/export fallback.
The sample query fails or returns different columnsReplace the example names with objects from your Memcached datastore, confirm the selected database / namespace, and keep the query bounded while you validate the result.