[Nikhil172913832]

Description

PostgreSQL folds unquoted identifiers to lowercase, causing "relation not found" errors when querying case-sensitive tables/columns created with quoted identifiers (e.g., CREATE TABLE "Notes"). This fix automatically quotes identifiers containing uppercase letters in the PostgreSQL dialect to preserve case according to PostgreSQL specification.

Changes:

• Modified sqlalchemy_render.py to auto-quote PostgreSQL identifiers with uppercase letters
• Updated tests to reflect correct PostgreSQL quoting behavior per official documentation

Fixes #11599

Type of change

(Please delete options that are not relevant)

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ⚡ New feature (non-breaking change which adds functionality)
• 📢 Breaking change (fix or feature that would cause existing functionality not to work as expected)
• 📄 This change requires a documentation update

Verification Process

To ensure the changes are working as expected:

• Test Location: tests/unit/render/test_sqlalchemyrender.py
• Verification Steps:
  1. Create a PostgreSQL table with quoted uppercase identifier: CREATE TABLE "Notes" (id INT, content TEXT)
  2. Query the table through MindsDB: SELECT * FROM Notes
  3. Verify the generated SQL quotes the identifier: SELECT * FROM "Notes" (preserves case)
  4. Run unit tests: python -m pytest tests/unit/render/test_sqlalchemyrender.py -v
  5. All 13 tests should pass

Additional Media:

• I have attached a brief loom video or screenshots showcasing the new functionality or change.

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.
• Relevant unit and integration tests are updated or added.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Nikhil172913832]

I have read the CLA Document and I hereby sign the CLA

[entelligence-ai-pr-reviews]

🔒 Entelligence AI Vulnerability Scanner

✅ No security vulnerabilities found!

Your code passed our comprehensive security analysis.

📊 Files Analyzed: 1 files

---

[Nikhil172913832]

Hi @ea-rus, just wanted to check if you could take a look at this PR when you get a chance.

[ea-rus]

we can't add quotes where they didn't existed before parsing
quotes should exist in input sql.
the problem is:

• if backticks are used in input sql - the query is rendered with doubleqoutes
• if doubleqoutes are used - the query doesn't have info about them and it is rendered without them

To fix it I came up to solution on the parser side: mindsdb/mindsdb_sql_parser#70

[ea-rus]

This update is not required, we won't support double quotes as escape symbols
mindsdb/mindsdb_sql_parser#84