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
Copy file name to clipboardexpand all lines: apps/docs/pages/guides/ai/engineering-for-scale.mdx
+4-4
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Content sources for vectors can be extremely large. As you grow you should run y
12
12
13
13
## Simple workloads
14
14
15
-
For small workloads it's typical to store your data in a single database.
15
+
For small workloads, it's typical to store your data in a single database.
16
16
17
17
If you've used [Vecs](/docs/guides/ai/vecs-python-client) to create 3 different collections, you can expose collections to your web or mobile application using [views](/docs/guides/database/tables#views):
18
18
@@ -93,9 +93,9 @@ docs.query(
93
93
94
94
### Accessing external collections using Wrappers
95
95
96
-
Supabase supports [Foreign Data Wrappers](/blog/postgres-foreign-data-wrappers-rust). Wrappers allow you connect two databases together so that you can query them over the network.
96
+
Supabase supports [Foreign Data Wrappers](/blog/postgres-foreign-data-wrappers-rust). Wrappers allow you to connect two databases together so that you can query them over the network.
97
97
98
-
This involves 2 steps: connecting to your remote database from the primary, and creating a Foreign Table.
98
+
This involves 2 steps: connecting to your remote database from the primary and creating a Foreign Table.
This diagram provides an example architecture, allowing you to access the collections either with our client libraries or using Vecs. You can add as many secondary databases as you need, in this example we show one only:
143
+
This diagram provides an example architecture that allows you to access the collections either with our client libraries or using Vecs. You can add as many secondary databases as you need (in this example we only show one):
Copy file name to clipboardexpand all lines: apps/docs/pages/guides/ai/managing-collections.mdx
+3-3
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ export const meta = {
7
7
sidebar_label: 'Managing collections',
8
8
}
9
9
10
-
A collection is an group of vector records managed by the `vecs` Python library. Records can be added to or updated in a collection. Collections can be queried at any time, but should be indexed for scalable query performance.
10
+
A collection is a group of vector records managed by the `vecs` Python library. Records can be added to or updated in a collection. Collections can be queried at any time, but should be indexed for scalable query performance.
11
11
12
12
Supabase provides a [Python client](/docs/guides/ai/vecs-python-client) called `vecs` for managing unstructured vector stores in Postgres. If you come from a data science background, this unstructured data approach will feel familiar. If you are more interested in a structured data approach, see [Vector columns](/docs/guides/ai/vector-columns) or read our guide on [Structured & Unstructured Embeddings](/docs/guides/ai/structured-unstructured-embeddings).
Collections can be queried immediately after being created.
76
76
However, for good performance, the collection should be indexed after records have been upserted.
77
77
78
-
Indexes should be created **after** the collection has been populated with records. Building an index on an empty collection will result in significantly reduced recall. Once the index has been created you can still upsert new documents into the collection but you should rebuild the index if the size of the collection more than doubles.
78
+
Indexes should be created **after** the collection has been populated with records. Building an index on an empty collection will significantly reduce recall. Once the index has been created you can still upsert new documents into the collection but you should rebuild the index if the size of the collection more than doubles.
79
79
80
80
Only one index may exist per-collection. By default, creating an index will replace any existing index.
This library supports the following tooling versions:
@@ -33,31 +25,10 @@ This library supports the following tooling versions:
33
25
34
26
Additionally, install the **React Auth Helpers** for components and hooks that can be used across all React-based frameworks.
35
27
36
-
```sh
28
+
```sh Terminal
37
29
npm install @supabase/auth-helpers-react
38
30
```
39
31
40
-
</TabPanel>
41
-
<TabPanelid="yarn"label="Yarn">
42
-
43
-
```sh
44
-
yarn add @supabase/auth-helpers-nextjs
45
-
```
46
-
47
-
This library supports the following tooling versions:
48
-
49
-
- Node.js: `^10.13.0 || >=12.0.0`
50
-
- Next.js: `>=10`
51
-
52
-
Additionally, install the **React Auth Helpers** for components and hooks that can be used across all React-based frameworks.
53
-
54
-
```sh
55
-
yarn add @supabase/auth-helpers-react
56
-
```
57
-
58
-
</TabPanel>
59
-
</Tabs>
60
-
61
32
## Set up environment variables
62
33
63
34
Retrieve your project URL and anon key in your project's [API settings](https://supabase.com/dashboard/project/_/settings/api) in the Dashboard to set up the following environment variables. For local development you can set them in a `.env.local` file. See an [example](https://github.com/supabase/auth-helpers/blob/main/examples/nextjs/.env.local.example).
Retrieve your project's URL and anon key from your [API settings](https://supabase.com/dashboard/project/_/settings/api), and create a `.env.local` file with the following environment variables:
This library supports the following tooling versions:
38
30
39
31
- Remix: `>=1.7.2`
40
32
41
-
</TabPanel>
42
-
<TabPanelid="yarn"label="Yarn">
43
-
44
-
```sh
45
-
yarn add @supabase/auth-helpers-remix
46
-
```
47
-
48
-
This library supports the following tooling versions:
49
-
50
-
- Remix: `>=1.7.2`
51
-
52
-
</TabPanel>
53
-
</Tabs>
54
-
55
33
## Set up environment variables
56
34
57
35
Retrieve your project URL and anon key in your project's [API settings](https://supabase.com/dashboard/project/_/settings/api) in the Dashboard to set up the following environment variables. For local development you can set them in a `.env` file. See an [example](https://github.com/supabase/auth-helpers/blob/main/examples/remix/.env.example).
0 commit comments