Guide

Engine Feature Notes

A place to document where behavior differs by engine before teams assume portability.

Updated 2026-03-11 · 4 min read

Jump to another doc

Do Not Assume Perfect Parity

Features such as SQL dialect support, explain behavior, schema tooling, and import/export semantics can vary by engine.

Validate Critical Workflows Per Engine

If a workflow is high-risk or performance-sensitive, verify it with the actual engine your team uses instead of assuming that one successful test generalizes cleanly.

Keep Notes Close To Operations

Reference notes are most useful when they explain how the difference changes real operator behavior, not just that the engines are technically different.

Related Docs

More in Reference / Engine Reference

Supported Databases

Overview of the engines and connection styles referenced in QuraMate docs and product messaging.

Reference · 4 min

Keyboard Shortcuts

A reference-oriented view of keyboard habits and high-signal editor workflows.

Reference · 3 min

Connection Parameters

Reference-style guidance for the inputs that matter most when saving a database profile.

Connection Reference · 5 min

Import & Export Formats

Choose formats based on reproducibility, tooling compatibility, and reviewability.

Data Reference · 4 min

SQL Editor Reference

Reference-oriented notes for formatting, execution modes, and editor discipline.

Feature Reference · 5 min

Result Grid Reference

Reference notes for result review, inline editing, and row-level confidence checks.

Feature Reference · 4 min