latticesql 3.2.0 → 3.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/dist/cli.js +6132 -4046
- package/dist/index.cjs +18800 -207
- package/dist/index.d.cts +160 -6
- package/dist/index.d.ts +160 -6
- package/dist/index.js +18801 -207
- package/docs/assistant.md +49 -11
- package/docs/cloud.md +85 -10
- package/docs/collaboration.md +5 -1
- package/docs/security.md +323 -0
- package/docs/workspaces.md +13 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -90,6 +90,8 @@ To use the Postgres backend (for Supabase, Neon, RDS, or any other Postgres-comp
|
|
|
90
90
|
npm install latticesql pg
|
|
91
91
|
```
|
|
92
92
|
|
|
93
|
+
> Deploying Lattice Cloud on managed Postgres (AWS RDS / RDS Proxy, Cloud SQL, Neon)? See the [managed-Postgres deployment notes](docs/cloud.md#deploying-on-managed-postgres-aws-rds--rds-proxy) — in particular, point the realtime `LISTEN` connection at a session-mode / direct endpoint, not a transaction-mode proxy.
|
|
94
|
+
|
|
93
95
|
Then pass a connection string instead of a file path:
|
|
94
96
|
|
|
95
97
|
```ts
|