XataX
Xata•16mo ago
Adam Harris

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 npx xata codegen, I'm now seeing errors because my records are coming back from the db (via the xata ts client) like this:
{
    id: 'rec_bla',
    ... my fields here
    xata_createdat: null,
    xata_id: null,
    xata_updatedat: null,
    xata_version: null,
    xata: {
      createdAt: 2024-09-04T15:26:12.400Z,
      updatedAt: 2024-09-04T15:26:12.400Z,
      version: 0
    }
}

whereas, before they were like this:

{
    ... my fields here
    xata_createdat: 2024-09-04T15:26:12.400Z,
    xata_id: 'rec_bla',
    xata_updatedat: 2024-09-04T15:26:12.400Z,
    xata_version: 0
}


The errors are happening because I was relying on the xata_id field, but it seems like the xata_id field now needs to be accessed at 
id
 and the other xata_ fields are now nested in a xata. path?

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_ postgres fields?
Was this page helpful?