Fixed Native Query API Response

[MinuraPunchihewa]

Description

This PR fixes the API response for native queries. The fact that this API errors out is causing the Minds API for querying data sources, which Anton relies on, to fail as well.

Type of change

• 🐛 Bug fix (non-breaking change which fixes an issue)

Verification Process

To ensure the changes are working as expected:

• Test Location: Specify the URL or path for testing.
• Verification Steps: Outline the steps or queries needed to validate the change. Include any data, configurations, or actions required to reproduce or see the new functionality.

Checklist:

• My code follows the style guidelines(PEP 8) of MindsDB.
• I have appropriately commented on my code, especially in complex areas.
• Necessary documentation updates are either made or tracked in issues - N/A
• Relevant unit and integration tests are updated or added.

[entelligence-ai-pr-reviews]

EntelligenceAI PR Summary

Refactors the post method in mindsdb/api/http/namespaces/sql.py to unify native and non-native query handling paths.

• Replaces raw query_response dicts with SQLAnswer objects in the native query branch for consistency
• Renames result to raw_result to prevent variable shadowing
• Introduces error_type distinction ('expected' vs 'unexpected') for error classification
• De-indents context retrieval and response formatting logic so it is shared across both the native-handler and process_query code paths

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR cleanly refactors the post method in mindsdb/api/http/namespaces/sql.py by unifying the native and non-native query handling paths, which reduces code duplication and improves maintainability. The introduction of SQLAnswer objects in the native query branch for consistency, renaming result to raw_result to prevent variable shadowing, and the error_type distinction between 'expected' and 'unexpected' errors are all well-scoped improvements with no identified logic regressions. No review comments were generated and heuristic analysis found zero critical, significant, or medium issues across the changed file.

Key Findings:

• The rename from result to raw_result in sql.py correctly eliminates a variable shadowing risk that could have caused subtle bugs when the outer result variable was referenced later in the shared code path.
• Replacing raw query_response dicts with SQLAnswer objects in the native query branch enforces a consistent contract for downstream response formatting, reducing the risk of missing fields or type mismatches.
• De-indenting the context retrieval and response formatting logic so it is shared across both native-handler and standard paths is a net reduction in duplicated code, lowering the surface area for future divergence bugs.
• Automated heuristic analysis found zero issues at any severity level across the single changed file, and no pre-existing unresolved comments were identified.

Files requiring special attention

• mindsdb/api/http/namespaces/sql.py

[ea-rus]

I think it should be in a release pr

[MinuraPunchihewa]

I just updated it to point to the release branch.