Live data from Hacker News

Postgres.new: In-browser Postgres with an AI interface

supabase.com

91–100 of 116 posts

Re: Postgres.new: In-browser Postgres with an AI interface

#91

Earlier quoted context omitted.

If I did that I would waste so much time. I know what code is in my codebase. Maybe if I was a novice this would be effective to help me learn it. Is the point of the exercise to wow myself for a week that an LLM can spit out solutions?

No its that it will code a days worth of work in a few minutes

Wow!

Re: Postgres.new: In-browser Postgres with an AI interface

#93
Very cool! What about projects/integrations with

- duckdb which also supports WASM - UWData's Mosaic (https://github.com/uwdata/mosaic) which supports real-time plots

would be really nice to have a kind of "drop-in" page that we could add to any intranet where people could just retrieve an export of some database, and plot it with your code

Re: Postgres.new: In-browser Postgres with an AI interface

#94

Clicking "New database" doesn't do anything for me...? No changes in the UI, and no messages in the console. Admittedly I'm not signed in with Github, but isn't that only for the AI thing (that really I don't want to use). Edit: Okay reading kiwicopple's comment makes it clearer that chatGPT is not-optional. I'm... not enthused by this. Why would you take something that's local-first and gatekeep it with something as…

(So uh, just to clarify for posterity, when I originally made this comment it was just a link to https://postgres.new/ without any description, and kiwicopple's comment was just a link to another comment of his on a related post. Obviously now there are more words, everywhere, explaining everything.)

(I still hate LLMs in my DB. I KNOW SQL LET ME WRITE IT.)

Re: Postgres.new: In-browser Postgres with an AI interface

#96
This tool is amazing for us. There's so many pieces to this - the capability is a big step forward for architecting databases.

Rudimentary compared to what you've done, but is it possible to take an existing database schema, developed either in the Supabase migrations style or another tool like Flyway, and draw the diagram? That alone is huge for us in an enterprise setting, and would allow us to communicate the structure of the database to business folks (especially large databases). How does the tool build that from migrations currently?

Re: Postgres.new: In-browser Postgres with an AI interface

#97
From the blog's section on semantic search:

  Under the hood, we store the embeddings in a meta.embeddings table then pass back to AI the resulting IDs for each embedding. We do this because embedding vectors are big, and sending these back and forth to the model is not only expensive, but also error prone. Instead, the language model is aware of the meta.embeddings table and simply subqueries to it when it needs access to an embedding.
A couple Qs if anyone knows:

1. What does it mean to "pass back to AI the resulting IDs for each embedding" but not the table rows corresponding to the matched vectors?

2. Does "the language model is aware of the meta.embedding table" mean Supabase has deployed a fine-tuned GPT-4o?

Re: Postgres.new: In-browser Postgres with an AI interface

#98

Earlier quoted context omitted.

If I did that I would waste so much time. I know what code is in my codebase. Maybe if I was a novice this would be effective to help me learn it. Is the point of the exercise to wow myself for a week that an LLM can spit out solutions?

No its that it will code a days worth of work in a few minutes

10x LoC is going to require more automation, to manage the sheer mass of it, which is more tools/money/layers of abstraction. AI coders need AI testers and AI peer reviewers, and need to iterate over and over to compensate for incorrectness to produce a working feature. That sounds hellishly inefficient. (but all it has to be is cheaper i suppose)

Re: Postgres.new: In-browser Postgres with an AI interface

#100

I really do think that software engineering as we know it is ending. It will take 3-5 years for tools like this to mature. But it will happen, and hard fought skill sets like SQL database design, query design, and maybe even ORMs will become obsolete. My biggest prediction is that ORMs will not be necessary when LLMs can generate SQL. Low level SQL is a better abstraction for LLMs than ORMs, and as people are removed…

> It will take 3-5 years for tools like this to mature. But it will happen, and hard fought skill sets like SQL database design, query design, and maybe even ORMs will become obsolete.

Until a query becomes a bottleneck and no one knows why because no one knows how databases work anymore.

Post reply on HN