Feature availability and limits
Verify the installed release
Section titled “Verify the installed release”particledb --versionparticledb start --helpRecord the server and client versions together. Examples checked against a source build do not automatically establish the behavior of an older downloaded package.
Distribution and version
Section titled “Distribution and version”The installation instructions use the standard downloadable server. Core query and Redis examples were checked with 1.1.19-rc.12.
| Capability | Standard 1.1.19-rc.12 binary |
|---|---|
| SQL clients, HTTP SQL and Redis clients | Included; use their separate connection addresses |
| Native client listener | Enabled by default; configure its address explicitly |
| Python Particles | Requires a separate Python-enabled distribution and matching authoring package |
| Transactional schema changes | Enabled by default on supported single-node transaction modes; see schema changes |
| Historical reads | Opt-in with --enable-time-travel; separate from backup and recovery |
The Python examples were checked with a Python-enabled server build. Do not expect the standard installer alone to provide that runtime.
Important boundaries
Section titled “Important boundaries”| Area | What to verify |
|---|---|
| Connections | The address for the selected client; not all interfaces share one listener |
| Transactions | Isolation, conflicts, schema commands and connection ownership |
| Data movement | Supported formats, server-side paths and export scope |
| Particles | Runtime inclusion, language support, dependencies and privileges |
| Agent workflows | Built-in execution versus application-managed worker patterns |
| Compatibility | Catalog queries, migration tools, extensions and lock semantics |
| Operations | Backup and restore commands included in your edition |
SQL compatibility
Section titled “SQL compatibility”An accepted connection or a parsed SQL statement is not proof that every behavior of another database is implemented. Test the exact operation, returned values and failure cases your application depends on.
Resource limits
Section titled “Resource limits”Memory, connection and execution limits depend on the configured server. See memory, connections and Particle limits.
Unsupported behavior
Section titled “Unsupported behavior”Treat a feature-not-supported error as a boundary to handle or redesign around. Do not remove safeguards or depend on silently ignored options to make a migration succeed.