Skip to content

refactor: Refactor AlloyDBEngine to depend on PGEngine #434

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

dishaprakash
Copy link
Contributor

@dishaprakash dishaprakash commented Jul 23, 2025

This PR refactors:

  • AlloyDBEngine to depend on PGEngine
  • Indexes to remove duplicate indexes

This PR also downgrades the pgvector dependency limit to below 0.4.0 (To keep it consistent with LangChain Postgres).

@dishaprakash dishaprakash requested review from a team as code owners July 23, 2025 08:31
@product-auto-label product-auto-label bot added the api: alloydb Issues related to the googleapis/langchain-google-alloydb-pg-python API. label Jul 23, 2025
@dishaprakash dishaprakash changed the title chore: Refactor AlloyDBEngine to depend on PGEngine refactor!: Refactor AlloyDBEngine to depend on PGEngine Jul 24, 2025
@dishaprakash dishaprakash changed the title refactor!: Refactor AlloyDBEngine to depend on PGEngine refactor: Refactor AlloyDBEngine to depend on PGEngine Aug 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: alloydb Issues related to the googleapis/langchain-google-alloydb-pg-python API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants