dbagent-cli 0.8.7__tar.gz → 0.8.8__tar.gz

{dbagent_cli-0.8.7 → dbagent_cli-0.8.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dbagent-cli
-Version: 0.8.7
+Version: 0.8.8
 Summary: Enterprise AI Database Copilot, Schema Graph Introspector & Autonomous Recovery Agent (CLI)
 Author: Santhosh Gupta
 Requires-Python: >=3.9

{dbagent_cli-0.8.7 → dbagent_cli-0.8.8}/dbagent/__init__.py

@@ -2,5 +2,5 @@
 DB-Agent: Universal Database Introspection and Script Generation AI Agent (CLI).
 """
 
-__version__ = "0.8.7"
+__version__ = "0.8.8"
 __author__ = "Santhosh Gupta"

{dbagent_cli-0.8.7 → dbagent_cli-0.8.8}/dbagent/agent/generator.py

@@ -47,17 +47,12 @@ Generate ONLY the raw executable SQL query for the given database. No markdown f
 {schema_context}
 
 ### Rules:
-1. Output ONLY the SQL query — nothing else. No ```sql fences, no explanations.
+1. Output ONLY the executable SQL query — nothing else. No ```sql fences, no explanations.
 2. Use the exact table and column names from the schema above.
 3. Use dialect-specific syntax for `{dialect_name}`.
 4. Write clean, optimized SQL with uppercase keywords.
-5. If the user asks for recent/time-based data, use native datetime functions (e.g. for PostgreSQL: `NOW() - INTERVAL '1 hour'`, for SQLite: `datetime('now', '-1 hour')`, for MySQL: `NOW() - INTERVAL 1 HOUR`).
-6. For queries inspecting PostgreSQL foreign key mappings or table relationships via system catalog, use standard joins:
-   SELECT tc.table_name, kcu.column_name, ccu.table_name AS foreign_table_name, ccu.column_name AS foreign_column_name
-   FROM information_schema.table_constraints tc
-   JOIN information_schema.key_column_usage kcu ON tc.constraint_name = kcu.constraint_name
-   JOIN information_schema.constraint_column_usage ccu ON tc.constraint_name = ccu.constraint_name
-   WHERE tc.constraint_type = 'FOREIGN KEY';
+5. Always query the user's actual database tables and junction/mapping tables from the schema context, using foreign key relationships for JOINs.
+6. If the user asks for recent/time-based data, use native datetime functions (e.g. for PostgreSQL: `NOW() - INTERVAL '1 hour'`, for SQLite: `datetime('now', '-1 hour')`, for MySQL: `NOW() - INTERVAL 1 HOUR`).
 7. Always include appropriate WHERE clauses, JOINs, and ORDER BY as needed.
 8. Default to LIMIT 50 unless the user specifies a count.
 9. For status, active, or flag columns (e.g. `active`, `is_active`, `status`, `enabled`, `deleted`):
@@ -86,7 +81,7 @@ You are chatting with the user in the interactive database shell.
 
 # --- Architectural / Linkage analysis prompt ---
 
-ARCHITECTURE_SYSTEM_PROMPT = """You are DB-Agent, a Principal Database Architect, Data Modeler, and Systems Engineer.
+ARCHITECTURE_SYSTEM_PROMPT = """You are DB-Agent, an elite Principal Database Architect, Data Modeler, and Systems Engineer.
 Target Database Context:
 - **Dialect**: {dialect_name}
 - **Database Name**: {database_name}
@@ -94,23 +89,16 @@ Target Database Context:
 ### Detailed Schema Sub-Graph Context (Tables, Columns, Primary Keys, Foreign Keys, Sample Data):
 {schema_context}
 
-The user is asking for architectural analysis, entity relationships, linkages, mappings, or how tables relate to each other in this database.
+The user is asking a question regarding database architecture, entity relationships, linkages, mappings, data flows, or structural design.
 
-Provide a comprehensive, high-quality, professional Architectural Report structured as follows:
+Analyze the provided schema and the user's question, and produce a clear, authoritative, and comprehensive architectural response structured as follows:
 
 ### 1. 🗺️ Entity-Relationship & Linkage Architecture Diagram
 Provide a clean, readable ASCII / Unicode box diagram showing the entities, relationship paths, cardinality (1:1, 1:N, N:M junction tables), and the exact connecting foreign keys / join keys.
-Example structure:
-```text
-┌──────────────┐          ┌──────────────────────┐          ┌───────────────┐
-│  ivis_user   │ 1 ──── * │ ivis_tenant_user_map │ * ──── 1 │  ivis_tenant  │
-└──────────────┘          └──────────────────────┘          └───────────────┘
-  (pk_user_id)                  (fk_user_id)                  (pk_tenant_id)
-```
 
 ### 2. 📐 Architectural & Theoretical Breakdown
-- Explain in clear theoretical and domain terms how the entities map to each other.
-- Highlight the mapping mechanism (direct foreign key vs junction/mapping table vs hierarchical tree).
+- Explain in clear theoretical and domain terms how the entities map to each other in this database.
+- Highlight the mapping mechanisms (direct foreign keys, junction/mapping tables, hierarchical ownership).
 - Detail the cardinality, tenant isolation, and user access models represented in the schema.
 
 ### 3. 🔍 How to Query & Verify Mappings (SQL Examples)

{dbagent_cli-0.8.7 → dbagent_cli-0.8.8}/dbagent_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dbagent-cli
-Version: 0.8.7
+Version: 0.8.8
 Summary: Enterprise AI Database Copilot, Schema Graph Introspector & Autonomous Recovery Agent (CLI)
 Author: Santhosh Gupta
 Requires-Python: >=3.9

{dbagent_cli-0.8.7 → dbagent_cli-0.8.8}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "dbagent-cli"
-version = "0.8.7"
+version = "0.8.8"
 description = "Enterprise AI Database Copilot, Schema Graph Introspector & Autonomous Recovery Agent (CLI)"
 readme = "README.md"
 requires-python = ">=3.9"