Cloud SQL is a fully managed relational database service that offers high performance, seamless integration, and impressive scalability. It offers MySQL, PostgreSQL, and SQL Server database engines. Extend your database application to build AI-powered experiences leveraging Cloud SQL’s LangChain integrations.This notebook goes over how to use Cloud SQL for MySQL to save, load and delete langchain documents with
MySQLLoader and MySQLDocumentSaver.
Learn more about the package on GitHub.
Before You Begin
To run this notebook, you will need to do the following:- Create a Google Cloud Project
- Enable the Cloud SQL Admin API.
- Create a Cloud SQL for MySQL instance
- Create a Cloud SQL database
- Add an IAM database user to the database (Optional)
🦜🔗 Library Installation
The integration lives in its ownlangchain-google-cloud-sql-mysql package, so we need to install it.
☁ Set Your Google Cloud Project
Set your Google Cloud project so that you can leverage Google Cloud resources within this notebook. If you don’t know your project ID, try the following:- Run
gcloud config list. - Run
gcloud projects list. - See the support page: Locate the project ID.
🔐 Authentication
Authenticate to Google Cloud as the IAM user logged into this notebook in order to access your Google Cloud Project.- If you are using Colab to run this notebook, use the cell below and continue.
- If you are using Vertex AI Workbench, check out the setup instructions here.
Basic Usage
MySQLEngine Connection Pool
Before saving or loading documents from MySQL table, we need first configures a connection pool to Cloud SQL database. TheMySQLEngine configures a connection pool to your Cloud SQL database, enabling successful connections from your application and following industry best practices.
To create a MySQLEngine using MySQLEngine.from_instance() you need to provide only 4 things:
project_id: Project ID of the Google Cloud Project where the Cloud SQL instance is located.region: Region where the Cloud SQL instance is located.instance: The name of the Cloud SQL instance.database: The name of the database to connect to on the Cloud SQL instance.
user and password arguments to MySQLEngine.from_instance():
user: Database user to use for built-in database authentication and loginpassword: Database password to use for built-in database authentication and login.
Initialize a table
Initialize a table of default schema viaMySQLEngine.init_document_table(<table_name>). Table Columns:
- page_content (type: text)
- langchain_metadata (type: JSON)
overwrite_existing=True flag means the newly initialized table will replace any existing table of the same name.
Save documents
Save langchain documents withMySQLDocumentSaver.add_documents(<documents>). To initialize MySQLDocumentSaver class you need to provide 2 things:
engine- An instance of aMySQLEngineengine.table_name- The name of the table within the Cloud SQL database to store langchain documents.
Load documents
Load langchain documents withMySQLLoader.load() or MySQLLoader.lazy_load(). lazy_load returns a generator that only queries database during the iteration. To initialize MySQLLoader class you need to provide:
engine- An instance of aMySQLEngineengine.table_name- The name of the table within the Cloud SQL database to store langchain documents.
Load documents via query
Other than loading documents from a table, we can also choose to load documents from a view generated from a SQL query. For example:Delete documents
Delete a list of langchain documents from MySQL table withMySQLDocumentSaver.delete(<documents>).
For table with default schema (page_content, langchain_metadata), the deletion criteria is:
A row should be deleted if there exists a document in the list, such that
document.page_contentequalsrow[page_content]document.metadataequalsrow[langchain_metadata]
Advanced Usage
Load documents with customized document page content & metadata
First we prepare an example table with non-default schema, and populate it with some arbitrary data.MySQLLoader from this example table, the page_content of loaded documents will be the first column of the table, and metadata will be consisting of key-value pairs of all the other columns.
content_columns and metadata_columns when initializing the MySQLLoader.
content_columns: The columns to write into thepage_contentof the document.metadata_columns: The columns to write into themetadataof the document.
content_columns will be joined together into a space-separated string, as page_content of loaded documents, and metadata of loaded documents will only contain key-value pairs of columns specified in metadata_columns.
Save document with customized page content & metadata
In order to save langchain document into table with customized metadata fields. We need first create such a table viaMySQLEngine.init_document_table(), and specify the list of metadata_columns we want it to have. In this example, the created table will have table columns:
- description (type: text): for storing fruit description.
- fruit_name (type text): for storing fruit name.
- organic (type tinyint(1)): to tell if the fruit is organic.
- other_metadata (type: JSON): for storing other metadata information of the fruit.
MySQLEngine.init_document_table() to create the table:
table_name: The name of the table within the Cloud SQL database to store langchain documents.metadata_columns: A list ofsqlalchemy.Columnindicating the list of metadata columns we need.content_column: The name of column to storepage_contentof langchain document. Default:page_content.metadata_json_column: The name of JSON column to store extrametadataof langchain document. Default:langchain_metadata.
MySQLDocumentSaver.add_documents(<documents>). As you can see in this example,
document.page_contentwill be saved intodescriptioncolumn.document.metadata.fruit_namewill be saved intofruit_namecolumn.document.metadata.organicwill be saved intoorganiccolumn.document.metadata.fruit_idwill be saved intoother_metadatacolumn in JSON format.
Delete documents with customized page content & metadata
We can also delete documents from table with customized metadata columns viaMySQLDocumentSaver.delete(<documents>). The deletion criteria is:
A row should be deleted if there exists a document in the list, such that
document.page_contentequalsrow[page_content]- For every metadata field
kindocument.metadatadocument.metadata[k]equalsrow[k]ordocument.metadata[k]equalsrow[langchain_metadata][k]
- There no extra metadata field presents in
rowbut not indocument.metadata.
Connect these docs programmatically to Claude, VSCode, and more via MCP for real-time answers.