You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing ideas and did not find a similar one
I added a very descriptive title
I've clearly described the feature request and motivation for it
Feature request
As a user of LangChain, I want to be able to specify a custom database schema at runtime when initializing the PGVector class.
This feature proposal aims to enhance the LangChain framework by enabling dynamic specification of database schema names when initializing the PGVector class. This functionality will allow users to set custom schemas for their database tables directly through the class constructor, thereby facilitating decoupling.
In current implementations of the LangChain framework, the database table name is hardcoded without a schema name being specified, therefore having it default to public. This makes the PGVector connector lack the flexibility needed for dynamic configuration during runtime. This limitation poses challenges such as in multi-tenant architectures where different clients or projects may require separate schemas.
It is frustrating to have to manually adjust the database schema within the codebase.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Checked
Feature request
As a user of LangChain, I want to be able to specify a custom database schema at runtime when initializing the PGVector class.
This feature proposal aims to enhance the LangChain framework by enabling dynamic specification of database schema names when initializing the PGVector class. This functionality will allow users to set custom schemas for their database tables directly through the class constructor, thereby facilitating decoupling.
Relevant Discussion: #18883
Motivation
In current implementations of the LangChain framework, the database table name is hardcoded without a schema name being specified, therefore having it default to
public
. This makes the PGVector connector lack the flexibility needed for dynamic configuration during runtime. This limitation poses challenges such as in multi-tenant architectures where different clients or projects may require separate schemas.It is frustrating to have to manually adjust the database schema within the codebase.
Proposal (If applicable)
No response
Beta Was this translation helpful? Give feedback.
All reactions