supabase
Feat: add support for initializing vecs client with custom schema
What kind of change does this PR introduce?
Feature: add support for connecting to a user-specified database schema (instead of hard-coding vecs).
This was accomplished by adding the schema argument to the Client class and replacing all hard-coded references to schema vecs.
Also added schema parameter to create_client method. For backwards compatibility, it still defaults to vecs.
What is the current behavior?
Currently, the client defaults to schema vecs. Users may want to place vecs collections under a schema according to their own naming conventions.
Addresses #62
Please link any relevant issues here.
What is the new behavior?
Users can now instantiate a Client instance with a custom schema. For example:
DB_CONNECTION = "postgresql://<user>:<password>@<host>:<port>/<db_name>"
# create vector store client
vx = vecs.create_client(DB_CONNECTION, schema="my_schema")
Additional context
Add any other context or screenshots.
Test coverage attached
@olirice thanks for the feedback! sure, I'm definitely up to implement that change.
