Xata internal postgres fields - can I rely on them?
Hi, I'm just trying to get started with Xata (with postgres enabled).
I chose to use prisma to manage the database schema and db migrations and the xata ts client/sdk for accessing the db.
All was going well and I decided to try and set up CI/CD properly, which included checking the xata files out of git and regenerating the client (using a prisma schema as source of truth) in the CI/CD pipeline.
However after trying to pin the versions of the client and cli in my package.json and running
whereas, before they were like this:
The errors are happening because I was relying on the
My guess is that I had the @next version of the client installed and had problems with it, so I installed the @latest, which might have caused this change in the xata fields...
Is this the case that the interface for accessing these fields has changed across versions of the client, and shouldn't I be relying on these
I chose to use prisma to manage the database schema and db migrations and the xata ts client/sdk for accessing the db.
All was going well and I decided to try and set up CI/CD properly, which included checking the xata files out of git and regenerating the client (using a prisma schema as source of truth) in the CI/CD pipeline.
However after trying to pin the versions of the client and cli in my package.json and running
npx xata codegenwhereas, before they were like this:
The errors are happening because I was relying on the
xata_idxata_ididxata_xata.My guess is that I had the @next version of the client installed and had problems with it, so I installed the @latest, which might have caused this change in the xata fields...
Is this the case that the interface for accessing these fields has changed across versions of the client, and shouldn't I be relying on these
xata_
