It'd be nice if it also included the queries for each use case, and had a better understanding of sharding. As is, I gave it a bunch of requirements, it created some tables. Was it sufficient? No idea, it didn't say what the query was for each requirement. Would it scale? Again, no idea without the queries. (But actually, no, it wouldn't have scaled; some requirements were impossible without cross-shard scans).

▲

encoderer a day ago | parent [-]

99% of apps never need to shard data. Probably closer to 99.9% if they are single tenant.

	▲	daxfohl a day ago \| parent [-]
		That seems off in my experience, but maybe it's different in different industries. Either way, working around sharding and scale seems like a place where a good AI could help provide recommendations and tradeoffs, so it's disappointing that the model doesn't seem to deal with it well. For basic relational schema design, I don't see much benefit of having AI.