|
|
|
|
|
by juleswritescode
452 days ago
|
|
Good question. If you rarely change your db, it'll probably not be as useful. But some platforms (such as Supabase) rely on many parts of Postgres. You use INSERT hooks to trigger queue insertions, Row Level Security (RLS) to secure data, SQL functions for aggregate queries. Plus the schema changes you do to support business use-cases. Normally, you'll write these things into SQL migration files. Without an LSP, you'd have to look up the current state/implementation of schemas/functions, and you'd have to run the migrations to see whether there are errors. With the LSP, that's easier. steinroe and I both use a lot of migrations in our day jobs (a whatsapp newsletter and a fintech startup). Hope this helps. |
|