Prisma arguably offers the best DX for database access. It would be nice if Xata offered first-class support for Prisma.

Provide an interface for GraphQL, reflecting the Xata/Postgres schema. Include docs and examples.

Include the total number of results in the response of paginated queries. Similar to https://feedback.xata.io/feature-requests/p/include-total-hits-in-search-response From Discord: https://discord.com/channels/996791218879086662/996791219348852836/1152677810842914887

Prisma schemas with their migration engine is what makes most developers use their technology. In production applications, Prisma isn't really an option because of its unoptimized way of handing queries (internal rust layer). Assuming Xata has handled this better and is production ready, adding an extension or NPM packages that can do the same but for your platform would be quite beneficial.

Add password field as a column type. Allow choosing password hash algorithm. Add password checking to SDK.

Store geolocation data (lat/lon coordinates) in a dedicated column type. Support geo bounding queries based on shapes (such us box) on geolocation columns.

Similar to the CLI's capability (xata init --schema filename.json, xata schema edit --source, xata schema upload schema.json) for creating or updating a database from an existing schema file, provide the option in the web UI to import schema from json in order to initiate or update a database/branch.

Currently for regular (not Gmail or Github) email login, Xata provides a magic link to login. Support setting a password and enabling 2FA.

Relating to https://feedback.xata.io/feature-requests/p/enhanced-many-to-many-relations-support for an N:M relation as a user I would like to choose which field from the linked records is presented in the UI to represent the relation (instead of the record id)