Загрузка видео...

Не удалось загрузить видео

На главную

I’m building an iOS app called Schema, a way to access databases when you’re away from your desk. Schema works with Postgres and MySQL. Here’s a teaser, and I’ll share some of the more clever UI over the coming weeks. I’m growing the size of the TestFlight. Reach out...

60,143 просмотров • 1 год назад •via X (Twitter)

Комментарии: 11

Фото профиля Caleb Panza ☾
Caleb Panza ☾1 год назад

Would love to check it out!!

Фото профиля Christian Esmann
Christian Esmann1 год назад

I just launched an all-in-one template for cross-platform development, based on the stack I use myself everyday. Expo, NextJS, TypeScript, Tailwind, Firebase, AppsFlyer, Authentication, Analytics, In-App Purchases, Stripe and a lot more, setup by default.

Фото профиля Hello I'm Robie 🚀
Hello I'm Robie 🚀1 год назад

I've been dreaming for an app like this while I'm on the go. LETS GOOOOOOOOO

Фото профиля Stephen Silber
Stephen Silber1 год назад

Want!

Фото профиля 🐦‍🔥
🐦‍🔥1 год назад

Need!!!

Фото профиля Dominic
Dominic1 год назад

Sent a DM.

Фото профиля Chase McCoy
Chase McCoy1 год назад

Would love to give this a shot 👋

Фото профиля Janny
Janny1 год назад

Would love access

Фото профиля paras360
paras3601 год назад

Would love access

Фото профиля Backseats
Backseats1 год назад

Want

Фото профиля Lennart Fischer
Lennart Fischer1 год назад

Looks and sounds great – would love to try it out!

Похожие видео

Big moment for Postgres! AI coding tools have been surprisingly bad at writing Postgres code. Not because the models are dumb, but because of how they learned SQL in the first place. LLMs are trained on the internet, which is full of outdated Stack Overflow answers and quick-fix tutorials. So when you ask an AI to generate a schema, it gives you something that technically runs but misses decades of Postgres evolution, like: - No GENERATED ALWAYS AS IDENTITY (added in PG10) - No expression or partial indexes - No NULLS NOT DISTINCT (PG15) - Missing CHECK constraints and proper foreign keys - Generic naming that tells you nothing But this is actually a solvable problem. You can teach AI tools to write better Postgres by giving them access to the right documentation at inference time. This exact solution is actually implemented in the newly released pg-aiguide by Tiger Data - Creators of TimescaleDB, which is an open-source MCP server that provides coding tools access to 35 years of Postgres expertise. In a gist, the MCP server enables: - Semantic search over the official PostgreSQL manual (version-aware, so it knows PG14 vs PG17 differences) - Curated skills with opinionated best practices for schema design, indexing, and constraints. I ran an experiment with Claude Code to see how well this works, and worked with the team to put this together. Prompt: "Generate a schema for an e-commerce site twice, one with the MCP server disabled, one with it enabled. Finally, run an assessment to compare the generated schemas." The run with the MCP server led to: - 420% more indexes (including partial and expression indexes) - 235% more constraints - 60% more tables (proper normalization) - 11 automation functions and triggers - Modern PG17 patterns throughout The MCP-assisted schema had proper data integrity, performance optimizations baked in, and followed naming conventions that actually make sense in production. pg-aiguide works with Claude Code, Cursor, VS Code, and any MCP-compatible tool. It's free and fully open source. I have shared the repo in the replies!

Avi Chawla

186,931 просмотров • 6 месяцев назад