How will it perform if I have 1TB of data?
Postgres.new: In-browser Postgres with an AI interface
21–30 of 116 posts
Re: Postgres.new: In-browser Postgres with an AI interface
#22Good work
Re: Postgres.new: In-browser Postgres with an AI interface
#23Hey Sam from Electric here, I work on PGlite What the team at Supabase have built with postgres.new is incredible, it has been a lot of fun to work with them on it over the last month or so. It's fead directly back into the development of PGlite and helped us iron out some bugs and finish hitting the feature list required. SQL databases and LLMs go together so incredible well, the structured data and schema enables a…
Re: Postgres.new: In-browser Postgres with an AI interface
#24I 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…
Giving everyone a smartphone with a great video camera built in didn't obsolete the field of cinematography. I don't think giving everyone tools to help them build software will obsolete software engineering.
I fear applications will suffer the same fate. "Good enough" will take over "well-architected".
Re: Postgres.new: In-browser Postgres with an AI interface
#25> Please connect from a laptop or desktop to use postgres.new. There's nothing wrong using Webkit / Safari on your laptop or desktop. There are dozens of us, DOZENS!
Re: Postgres.new: In-browser Postgres with an AI interface
#26> Please connect from a laptop or desktop to use postgres.new. There's nothing wrong using Webkit / Safari on your laptop or desktop. There are dozens of us, DOZENS!
It throws an error when its full screen though. There is more to the error, but it wont let me copy it.
indexDB.databases is not a function.Re: Postgres.new: In-browser Postgres with an AI interface
#27> Please connect from a laptop or desktop to use postgres.new. There's nothing wrong using Webkit / Safari on your laptop or desktop. There are dozens of us, DOZENS!
1/ you're using a small window (even on Chrome/FF). We don't support mobile yet, so if you're seeing this on a desktop just expand the window
2/ you're on safari, which doesn't have support for OPFS yet: https://github.com/electric-sql/pglite/pull/130
Re: Postgres.new: In-browser Postgres with an AI interface
#28> Please connect from a laptop or desktop to use postgres.new. There's nothing wrong using Webkit / Safari on your laptop or desktop. There are dozens of us, DOZENS!
Why not just display a warning and let me try anyway? How sure are they that their filtering out absolutely every device that can't run it successfully. Why risk denying it unnecessarily?
Re: Postgres.new: In-browser Postgres with an AI interface
#29- a customer orders database with products with a timeseries of prices, and multiple fulfilments per order. - an issue tracking system with a reflexive user/manager database - a family relationship model
In each case I got it to put in sample model and then asked postgres.new to answer some questions about the data it had inserted. I thought the family model would trip it up, especially when I told it to put in cousins and uncles. But no, it was pretty bang on.
The only thing it didn't quite manage is that some of the relationships are reciprocal (i.e. my sibling also has me as a sibling).
I asked postgres.new to review the data and it fixed some, and i asked it to check again and it fixed the rest. This is a very useful tool that I can see myself using!
Re: Postgres.new: In-browser Postgres with an AI interface
#30I 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…
LLMs don't have the context to make good decisions though. You need all of that hard fought skills to make those decisions. And people are the only ones that can have the context enough to actually make decisions. Not only that, but AI is way more expensive than we think. We're currently in a hype bubble funded by last ditch effort VC money. When that money runs out, and it will eventually, AI is going to get WAY mor…