google-cloud-db-context-engineering 0.7.1__tar.gz → 0.7.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (30) hide show
  1. {google_cloud_db_context_engineering-0.7.1/src/google_cloud_db_context_engineering.egg-info → google_cloud_db_context_engineering-0.7.2}/PKG-INFO +8 -8
  2. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/README.md +7 -7
  3. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/pyproject.toml +1 -1
  4. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2/src/google_cloud_db_context_engineering.egg-info}/PKG-INFO +8 -8
  5. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/LICENSE +0 -0
  6. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/setup.cfg +0 -0
  7. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/__init__.py +0 -0
  8. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/common/__init__.py +0 -0
  9. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/common/config.py +0 -0
  10. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/common/context_mutator.py +0 -0
  11. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/common/context_store_client.py +0 -0
  12. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/dataset/__init__.py +0 -0
  13. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/dataset/dataset_generator.py +0 -0
  14. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/evaluate/__init__.py +0 -0
  15. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/evaluate/db_generators/__init__.py +0 -0
  16. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/evaluate/db_generators/alloydb.py +0 -0
  17. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/evaluate/db_generators/base.py +0 -0
  18. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/evaluate/db_generators/mysql.py +0 -0
  19. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/evaluate/db_generators/postgres.py +0 -0
  20. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/evaluate/db_generators/spanner.py +0 -0
  21. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/evaluate/evaluate_generator.py +0 -0
  22. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/evaluate/result_reader.py +0 -0
  23. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/main.py +0 -0
  24. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/model/__init__.py +0 -0
  25. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google/cloud/db_context_enrichment/model/context.py +0 -0
  26. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google_cloud_db_context_engineering.egg-info/SOURCES.txt +0 -0
  27. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google_cloud_db_context_engineering.egg-info/dependency_links.txt +0 -0
  28. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google_cloud_db_context_engineering.egg-info/entry_points.txt +0 -0
  29. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google_cloud_db_context_engineering.egg-info/requires.txt +0 -0
  30. {google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/src/google_cloud_db_context_engineering.egg-info/top_level.txt +0 -0
{google_cloud_db_context_engineering-0.7.1/src/google_cloud_db_context_engineering.egg-info → google_cloud_db_context_engineering-0.7.2}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: google-cloud-db-context-engineering
3
- Version: 0.7.1
3
+ Version: 0.7.2
4
4
  Summary: A FastMCP server for generating natural language to SQL templates from database schemas.
5
5
  Requires-Python: >=3.12
6
6
  Description-Content-Type: text/markdown
@@ -20,25 +20,25 @@ This is not an officially supported Google product. This project is not eligible
20
20
 
21
21
  # Context Engineering Agent
22
22
 
23
- The **Context Engineering Agent** is an AI coding agent plugin designed to run in developer agent harnesses (such as Claude Code, Antigravity, or Gemini CLI). It generates, evaluates, and iteratively tunes tailored context artifacts (`ContextSets` comprising `Templates`, `Facets`, and `Value Searches`) to enrich database schemas for **Gemini Data Analytics's data agent developer platform tools**, such as QueryData ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/data-agent-overview) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/data-agent-overview) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/data-agent-overview) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/data-agent-overview)).
23
+ The **Context Engineering Agent** is an AI coding agent plugin designed to run in developer agent harnesses (such as Claude Code, Antigravity, or Gemini CLI). It generates, evaluates, and iteratively tunes tailored context artifacts (`ContextSets` comprising `Templates`, `Facets`, and `Value Searches`) to enrich database schemas for **Gemini Data Analytics's data agent developer platform tools**, supporting both **relational SQL** and **Graph Query Language (GQL)** across [AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/data-agent-overview), Cloud SQL ([PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/data-agent-overview) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/data-agent-overview)), and [Cloud Spanner (GoogleSQL & Spanner Graph)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/data-agent-overview).
24
24
 
25
25
  ---
26
26
 
27
27
  ## Why Context Engineering?
28
28
 
29
- When building data agents and natural language analytics interfaces, accurately translating user intent into database queries is critical.
29
+ When building data agents and natural language analytics interfaces, accurately translating user intent into database queries—whether relational SQL, pure GQL, or hybrid graph queries—is critical.
30
30
 
31
- As outlined in **Build Context with Context Engineering Agent** ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/build-context-gemini-cli) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/build-context-gemini-cli) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/build-context-gemini-cli) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/build-context-gemini-cli)), by optimizing a `ContextSet` to match your application's expected query stream, the **QueryData API** acts as a data agent tool capable of achieving **~100% NL-to-SQL translation accuracy with low latency**.
31
+ As outlined in **Build Context with Context Engineering Agent** ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/build-context-gemini-cli) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/build-context-gemini-cli) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/build-context-gemini-cli) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/build-context-gemini-cli)), by optimizing a `ContextSet` to match your application's expected query stream, the **QueryData API** acts as a data agent tool capable of achieving **~100% NL-to-SQL/GQL translation accuracy with low latency**.
32
32
 
33
33
  ---
34
34
 
35
35
  ## Core Concepts
36
36
 
37
- A `ContextSet` is the central artifact generated and managed by the agent, containing structured knowledge in three primary forms:
37
+ A `ContextSet` is the central artifact generated and managed by the agent, containing structured knowledge across SQL and GQL query domains in three primary forms:
38
38
 
39
- * **Templates**: Link natural language query patterns to complete query statements.
40
- * **Facets**: Reusable, modular query fragments (e.g., parameterized `WHERE` clauses or specialized join filters) linked to domain vocabulary.
41
- * **Value Searches**: Specialized mapping queries that dynamically resolve user-supplied values (e.g., *"Lndn"*) to database records (*"London"*) via the capabilities of the underlying database, such as embedding search, AI operators, or simple trigram search.
39
+ * **Templates**: Link natural language query patterns to complete query statements (supporting relational SQL, pure GQL with `GRAPH ... MATCH`, and hybrid `GRAPH_TABLE` queries for Spanner Graph).
40
+ * **Facets**: Reusable, modular query fragments (e.g., parameterized `WHERE` clauses, specialized join filters, or graph `MATCH` traversal patterns) linked to domain vocabulary.
41
+ * **Value Searches**: Specialized mapping queries that dynamically resolve user-supplied values (e.g., *"Lndn"*) to database records (*"London"*) via the capabilities of the underlying database, such as embedding search, AI operators, or trigram search on relational and graph property tables.
42
42
 
43
43
  For full schema details, structure specifications, and dialect-specific JSON representations of `ContextSets`, see the official **Context Sets Overview** ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/context-sets-overview) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/context-sets-overview) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/context-sets-overview) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/context-sets-overview)).
44
44
 
{google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/README.md RENAMED
@@ -2,25 +2,25 @@ This is not an officially supported Google product. This project is not eligible
2
2
 
3
3
  # Context Engineering Agent
4
4
 
5
- The **Context Engineering Agent** is an AI coding agent plugin designed to run in developer agent harnesses (such as Claude Code, Antigravity, or Gemini CLI). It generates, evaluates, and iteratively tunes tailored context artifacts (`ContextSets` comprising `Templates`, `Facets`, and `Value Searches`) to enrich database schemas for **Gemini Data Analytics's data agent developer platform tools**, such as QueryData ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/data-agent-overview) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/data-agent-overview) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/data-agent-overview) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/data-agent-overview)).
5
+ The **Context Engineering Agent** is an AI coding agent plugin designed to run in developer agent harnesses (such as Claude Code, Antigravity, or Gemini CLI). It generates, evaluates, and iteratively tunes tailored context artifacts (`ContextSets` comprising `Templates`, `Facets`, and `Value Searches`) to enrich database schemas for **Gemini Data Analytics's data agent developer platform tools**, supporting both **relational SQL** and **Graph Query Language (GQL)** across [AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/data-agent-overview), Cloud SQL ([PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/data-agent-overview) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/data-agent-overview)), and [Cloud Spanner (GoogleSQL & Spanner Graph)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/data-agent-overview).
6
6
 
7
7
  ---
8
8
 
9
9
  ## Why Context Engineering?
10
10
 
11
- When building data agents and natural language analytics interfaces, accurately translating user intent into database queries is critical.
11
+ When building data agents and natural language analytics interfaces, accurately translating user intent into database queries—whether relational SQL, pure GQL, or hybrid graph queries—is critical.
12
12
 
13
- As outlined in **Build Context with Context Engineering Agent** ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/build-context-gemini-cli) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/build-context-gemini-cli) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/build-context-gemini-cli) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/build-context-gemini-cli)), by optimizing a `ContextSet` to match your application's expected query stream, the **QueryData API** acts as a data agent tool capable of achieving **~100% NL-to-SQL translation accuracy with low latency**.
13
+ As outlined in **Build Context with Context Engineering Agent** ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/build-context-gemini-cli) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/build-context-gemini-cli) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/build-context-gemini-cli) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/build-context-gemini-cli)), by optimizing a `ContextSet` to match your application's expected query stream, the **QueryData API** acts as a data agent tool capable of achieving **~100% NL-to-SQL/GQL translation accuracy with low latency**.
14
14
 
15
15
  ---
16
16
 
17
17
  ## Core Concepts
18
18
 
19
- A `ContextSet` is the central artifact generated and managed by the agent, containing structured knowledge in three primary forms:
19
+ A `ContextSet` is the central artifact generated and managed by the agent, containing structured knowledge across SQL and GQL query domains in three primary forms:
20
20
 
21
- * **Templates**: Link natural language query patterns to complete query statements.
22
- * **Facets**: Reusable, modular query fragments (e.g., parameterized `WHERE` clauses or specialized join filters) linked to domain vocabulary.
23
- * **Value Searches**: Specialized mapping queries that dynamically resolve user-supplied values (e.g., *"Lndn"*) to database records (*"London"*) via the capabilities of the underlying database, such as embedding search, AI operators, or simple trigram search.
21
+ * **Templates**: Link natural language query patterns to complete query statements (supporting relational SQL, pure GQL with `GRAPH ... MATCH`, and hybrid `GRAPH_TABLE` queries for Spanner Graph).
22
+ * **Facets**: Reusable, modular query fragments (e.g., parameterized `WHERE` clauses, specialized join filters, or graph `MATCH` traversal patterns) linked to domain vocabulary.
23
+ * **Value Searches**: Specialized mapping queries that dynamically resolve user-supplied values (e.g., *"Lndn"*) to database records (*"London"*) via the capabilities of the underlying database, such as embedding search, AI operators, or trigram search on relational and graph property tables.
24
24
 
25
25
  For full schema details, structure specifications, and dialect-specific JSON representations of `ContextSets`, see the official **Context Sets Overview** ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/context-sets-overview) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/context-sets-overview) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/context-sets-overview) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/context-sets-overview)).
26
26
 
{google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2}/pyproject.toml RENAMED
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "google-cloud-db-context-engineering"
3
- version = "0.7.1"
3
+ version = "0.7.2"
4
4
  description = "A FastMCP server for generating natural language to SQL templates from database schemas."
5
5
  readme = "README.md"
6
6
  requires-python = ">=3.12"
{google_cloud_db_context_engineering-0.7.1 → google_cloud_db_context_engineering-0.7.2/src/google_cloud_db_context_engineering.egg-info}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: google-cloud-db-context-engineering
3
- Version: 0.7.1
3
+ Version: 0.7.2
4
4
  Summary: A FastMCP server for generating natural language to SQL templates from database schemas.
5
5
  Requires-Python: >=3.12
6
6
  Description-Content-Type: text/markdown
@@ -20,25 +20,25 @@ This is not an officially supported Google product. This project is not eligible
20
20
 
21
21
  # Context Engineering Agent
22
22
 
23
- The **Context Engineering Agent** is an AI coding agent plugin designed to run in developer agent harnesses (such as Claude Code, Antigravity, or Gemini CLI). It generates, evaluates, and iteratively tunes tailored context artifacts (`ContextSets` comprising `Templates`, `Facets`, and `Value Searches`) to enrich database schemas for **Gemini Data Analytics's data agent developer platform tools**, such as QueryData ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/data-agent-overview) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/data-agent-overview) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/data-agent-overview) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/data-agent-overview)).
23
+ The **Context Engineering Agent** is an AI coding agent plugin designed to run in developer agent harnesses (such as Claude Code, Antigravity, or Gemini CLI). It generates, evaluates, and iteratively tunes tailored context artifacts (`ContextSets` comprising `Templates`, `Facets`, and `Value Searches`) to enrich database schemas for **Gemini Data Analytics's data agent developer platform tools**, supporting both **relational SQL** and **Graph Query Language (GQL)** across [AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/data-agent-overview), Cloud SQL ([PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/data-agent-overview) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/data-agent-overview)), and [Cloud Spanner (GoogleSQL & Spanner Graph)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/data-agent-overview).
24
24
 
25
25
  ---
26
26
 
27
27
  ## Why Context Engineering?
28
28
 
29
- When building data agents and natural language analytics interfaces, accurately translating user intent into database queries is critical.
29
+ When building data agents and natural language analytics interfaces, accurately translating user intent into database queries—whether relational SQL, pure GQL, or hybrid graph queries—is critical.
30
30
 
31
- As outlined in **Build Context with Context Engineering Agent** ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/build-context-gemini-cli) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/build-context-gemini-cli) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/build-context-gemini-cli) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/build-context-gemini-cli)), by optimizing a `ContextSet` to match your application's expected query stream, the **QueryData API** acts as a data agent tool capable of achieving **~100% NL-to-SQL translation accuracy with low latency**.
31
+ As outlined in **Build Context with Context Engineering Agent** ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/build-context-gemini-cli) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/build-context-gemini-cli) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/build-context-gemini-cli) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/build-context-gemini-cli)), by optimizing a `ContextSet` to match your application's expected query stream, the **QueryData API** acts as a data agent tool capable of achieving **~100% NL-to-SQL/GQL translation accuracy with low latency**.
32
32
 
33
33
  ---
34
34
 
35
35
  ## Core Concepts
36
36
 
37
- A `ContextSet` is the central artifact generated and managed by the agent, containing structured knowledge in three primary forms:
37
+ A `ContextSet` is the central artifact generated and managed by the agent, containing structured knowledge across SQL and GQL query domains in three primary forms:
38
38
 
39
- * **Templates**: Link natural language query patterns to complete query statements.
40
- * **Facets**: Reusable, modular query fragments (e.g., parameterized `WHERE` clauses or specialized join filters) linked to domain vocabulary.
41
- * **Value Searches**: Specialized mapping queries that dynamically resolve user-supplied values (e.g., *"Lndn"*) to database records (*"London"*) via the capabilities of the underlying database, such as embedding search, AI operators, or simple trigram search.
39
+ * **Templates**: Link natural language query patterns to complete query statements (supporting relational SQL, pure GQL with `GRAPH ... MATCH`, and hybrid `GRAPH_TABLE` queries for Spanner Graph).
40
+ * **Facets**: Reusable, modular query fragments (e.g., parameterized `WHERE` clauses, specialized join filters, or graph `MATCH` traversal patterns) linked to domain vocabulary.
41
+ * **Value Searches**: Specialized mapping queries that dynamically resolve user-supplied values (e.g., *"Lndn"*) to database records (*"London"*) via the capabilities of the underlying database, such as embedding search, AI operators, or trigram search on relational and graph property tables.
42
42
 
43
43
  For full schema details, structure specifications, and dialect-specific JSON representations of `ContextSets`, see the official **Context Sets Overview** ([AlloyDB](https://docs.cloud.google.com/gemini/data-agents/querydata/alloydb/context-sets-overview) | Cloud SQL: [PostgreSQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-postgres/context-sets-overview) / [MySQL](https://docs.cloud.google.com/gemini/data-agents/querydata/sql-mysql/context-sets-overview) | [Spanner (GoogleSQL)](https://docs.cloud.google.com/gemini/data-agents/querydata/spanner/context-sets-overview)).
44
44