I gave it a tool to execute to get that info if required, but it mostly doesn’t need to due to Kysely migration files and the database type definition being enough.

Claude code figures that out at startup every time. Never had issues with it.

You can save some precious context by having it somewhere without it having to figure it out from scratch every time.

Do you not use a model file for your orm?

ORMs are generally a bad idea, so.. hopefully not?

Even without the explicit magic ORMs, with data mapper style query builders like Kysely and similar, I still find I need to marshall selected rows into objects to, yknow, do things with them in a lot of cases.

Perhaps a function of GraphQL though.

Sure, but that's not the same thing. For example, whether or not you have to redeclare your entire database schema in a custom ORM language in a different repo.

This isn't the 00s any more.