Query Builder limitations with SQLite in-memory integration testing

CodeIgniter 4 enables database-agnostic query construction through its Query Builder, allowing developers to run integration tests using an SQLite in-memory database via the DatabaseTrait. This approach facilitates testing CRUD logic without requiring production credentials or a live database server.

The challenge arises when the application relies on database-specific SQL features that are not universally supported across engines. While the Query Builder abstracts standard operations seamlessly, advanced features like JSONB operations or specific spatial functions may fail or behave differently when switching from a MySQL or PostgreSQL production environment to SQLite.

How does the Query Builder handle non-standard SQL syntax when the test environment is toggled to SQLite in-memory? Are there specific patterns within the framework to ensure compatibility for JSON-specific queries without rewriting the core query logic?