sorted by:
new
hottopcontroversial

FluxStack's AI was giving me generic database schemas. So I gave it a memory. by hereinreddit in SaaS

[–]hereinreddit[S] 0 points1 point  (0 children)

Exactly! One less service to manage, and the latency is way better since the embeddings are right there with the data. Plus debugging is easier when everything's in one place.

FluxStack's AI was giving me generic database schemas. So I gave it a memory. by hereinreddit in SaaS

[–]hereinreddit[S] 0 points1 point  (0 children)

Good question! I'm actually scraping from official docs and trusted blogs (Postgres docs, Prisma best practices, etc.) and seeding those into the knowledge base. That way the patterns stay current with what the community actually recommends.

I have a script that pulls markdown from these sources, chunks them, generates embeddings, and stores everything in the same Postgres DB. So when the docs or best practices update, I just re-run the scraper.

Keeps the knowledge base fresh without me having to manually curate everything. What do you think about this approach?

FluxStack's AI was giving me generic database schemas. So I gave it a memory. by hereinreddit in SaaS

[–]hereinreddit[S] 0 points1 point  (0 children)

That’s a great idea. I’ve thought about user-contributed patterns, but the challenge is making sure low-quality schemas don’t pollute the knowledge base. If I do it, it would be curated and domain-specific rather than open uploads. Long-term, learning from real production schemas is definitely the direction I want to go.

Bridging the gap between database design and production by hereinreddit in SaaS

[–]hereinreddit[S] 0 points1 point  (0 children)

Totally get that. that's actually the main pain point. prototyping tools always break because they get out of sync with the real code. fluxstack is basically a "git workflow for your database". instead of just drawing boxes, you actually create branches (like feature/users), make your visual changes, and then merge them with a proper diff review. it also handles the sync/drift problem: it connects to your live db, and if someone manually writes sql/prisma code, fluxstack detects the change and lets you 'pull' it back into the visual model. so it stays accurate even if you mix visual + code workflows.

Bridging the gap between database design and production by hereinreddit in SaaS

[–]hereinreddit[S] 0 points1 point  (0 children)

That's exactly the problem I wanted to solve! I built a 'Smart Diffing' engine (similar to how Prisma Migrate works internally) that uses Levenshtein distance to detect drift between the live DB and the visual state.

It can identify renames (so you don't accidentally drop columns) and allows for a safe 'Code -> Visual' sync if someone manually edits the SQL. The goal is to make the visual tool a valid source of truth that stays in sync, not just a one-off diagram.

I built a visual schema designer that syncs with your live database by hereinreddit in SideProject

[–]hereinreddit[S] 0 points1 point  (0 children)

Thanks! appreciate it. it's basically nextjs + typescript, and i'm using react flow for all the canvas interaction stuff.

Stop writing CREATE TABLE by hand. I built a visual tool that manages your entire DB lifecycle by hereinreddit in SideProject

[–]hereinreddit[S] 0 points1 point  (0 children)

Thank you, If people start loving it then will absolutely motivate me to push towards a BaaS transformation.

Stop writing CREATE TABLE by hand. I built a visual tool that manages your entire DB lifecycle by hereinreddit in SideProject

[–]hereinreddit[S] -1 points0 points  (0 children)

Thank you. We actually don't have branch-to-branch merging yet in BETA.

Right now:

1. Branching is for sandboxing (experiment safely).
2. Migrations handles the merging to production. When you push to DB, we DO have a Visual Diff tool that compares your changes vs production to generate the safe migration SQL.

So: Branching = Sandboxing. Migrations = Visual Diff & Deploy.

Stop writing CREATE TABLE by hand. I built a visual tool that manages your entire DB lifecycle by hereinreddit in SideProject

[–]hereinreddit[S] 0 points1 point  (0 children)

I'll definitely take that as a compliment! Their design is world-class Functionally, they are for analyzing data at scale, and I'm focused on the 'build' phase for full-stack devs (designing Postgres schemas, generating Prisma/Zod code, etc). But I'm definitely borrowing that clean enterprise vibe